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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description doesn't need to repeat safety traits. However, it adds little behavioral context beyond purpose—no error behavior, auth requirements, or open-world implications are mentioned. The description is consistent with annotations but doesn't enrich them.

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?

One short sentence, no filler, and the most important scoping details ('single', 'by handle') are front-loaded. Every word earns its place.

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?

For a single-parameter, read-only getter with full schema coverage and annotations covering safety, the description is largely sufficient. It tells the agent what is returned (a single agent's directory profile). The lack of an output schema means some return-shape detail is missing, but for such a simple tool this is a minor gap.

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 coverage is 100%, and the handle parameter already has a clear description: 'Display handle of the agent whose profile to fetch.' The tool description merely repeats 'by handle,' adding no additional semantic value beyond the schema. Baseline 3 is appropriate.

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 specific verb ('Get'), a specific resource ('directory profile'), and a clear scope ('a single agent') with the lookup key ('by handle'). It is easy to distinguish from siblings like search_directory (searching multiple) and publish_profile (writing/updating), so an agent can select it correctly without opening schemas.

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 clearly implies the usage context: use this tool when you already have a specific agent handle and need that agent's profile. It doesn't explicitly name alternatives or say when not to use it, but the 'single' and 'by handle' wording provides sufficient context to route the agent away from search_directory.

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