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

Annotations already establish that this is a safe, read-only, idempotent operation. The description adds meaningful behavioral context beyond annotations by disclosing that pending candidates are included with directory_scope, identity conflicts and unknowns, that illustrated channels are excluded, and that candidate inclusion does not confirm AI production or video format.

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?

The description is front-loaded with the core retrieval purpose and then adds scoping and caveat sentences. It is compact and mostly efficient, though the second and third sentences are dense with domain-specific terms.

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?

An output schema exists, so return-value details need not be fully restated, and annotations cover the safety profile. The description is complete enough for calling the tool, but it omits how to obtain the required ID and what happens if the profile is not found.

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?

There is one parameter, id, and the schema provides 0% description coverage. The description partially compensates by clarifying that id means an exact directory profile ID, but it does not specify format, source, case sensitivity, or how to look up the ID.

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 uses a specific verb, "Retrieve," and names the resource precisely: one exact directory profile ID with its research record and referenced sources. It implicitly distinguishes this lookup-by-ID tool from search-oriented siblings, but it does not explicitly name search_ai_monks or other alternatives.

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 phrase "one exact directory profile ID" implies this tool should be used when an exact ID is already known, but the description never explicitly states when to use it versus search_ai_monks or how to obtain the ID. Usage is therefore implied rather than clearly guided.

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