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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so safety is covered. The description adds value by disclosing the return fields (name, email addresses, affiliated organizations) and specifying the source domain (IETF Datatracker), which is beyond the structured metadata. No contradictions with annotations.

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 a single, front-loaded sentence that efficiently conveys the action, resource, parameter, and return payload. Every word contributes value, with no redundancy or filler.

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 simple one-parameter fetch tool with a rich annotation set and an output schema, the description covers all necessary context: what it fetches, how (by numeric ID), and what it returns. No additional behavioral or procedural details are needed.

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?

With schema coverage at 0%, the description must clarify parameter meaning. It does so by saying 'by numeric ID', which explains that the 'id' parameter is a numeric IETF Datatracker identifier, not an arbitrary number. This adds meaningful context beyond the schema's bare 'type: number'.

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 specifically states 'Fetch an IETF Datatracker person record by numeric ID', using a clear verb and resource, and distinguishes itself from sibling tools like rfc, wg, and document by targeting person records. It also specifies the return content (name, email addresses, affiliated organizations), making the purpose fully unambiguous.

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 implies usage context: use this when you have a numeric IETF Datatracker person ID. However, it does not explicitly mention alternatives or when not to use it, especially relative to similar-looking siblings such as entity_profile or resolve_entity. The context is clear but lacks explicit exclusions or alternative guidance.

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