Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the burden of behavioral disclosure. It signals a non-mutating read operation and full-framework scope, but it does not explain identifier precedence, handling of missing or multiple identifiers, authentication needs, or error behavior. This is acceptable for a simple read but leaves meaningful gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

A single, dense sentence that front-loads the core purpose and then lists lookup keys. Every word contributes value; there is no repetition, filler, or irrelevant detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the essential purpose and identifiers, but with no annotations, no output schema, and no required parameters, it should provide more guidance on return shape, identifier requirements, and how it differs from get_my_profile. The core is present, but an agent must infer key calling constraints.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must explain the parameters. It names all three parameters and indicates they are lookup identifiers, which adds real meaning. However, it does not state that at least one identifier is required, nor what happens if more than one is provided, leaving ambiguity in call construction.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear verb ('read'), a specific target ('one person'), a breadth ('Full 21-framework'), and the available lookup keys ('profile_id, email, or name'). This distinguishes it from siblings like list_profiles and get_my_profile by emphasizing an individual, comprehensive read.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear context: use this tool when you need a full framework read for a single person identified by one of three values. It does not explicitly name alternatives or exclusions, but the 'one person' scope strongly implies list_profiles for multiple people and get_my_profile for the current user.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.