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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds the behavioral context that each row includes the generated_unique_award_id for chaining, and that the award_id must be an IDV-generated unique ID. This goes beyond the annotations by explaining the output linkage and the input constraint, which is valuable for the agent's understanding of how results can be used.

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 two sentences with zero waste. The first sentence states the core purpose, and the second provides essential input requirements and chaining information. It is front-loaded with the most critical information and structured logically, earning its place without any redundancy.

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?

Given the tool's 6 parameters and the presence of an output schema, the description covers the essential operational context: what it returns (rows with generated_unique_award_id), how to obtain the required parent ID, and the relationship to other tools. It does not need to explain the output schema since that exists separately. The only slight gap is that it doesn't explicitly state behavior for non-IDV inputs, but it implies the tool is for IDV awards. Overall, it is complete for an agent to call correctly.

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 100%, so the baseline is 3. The description adds significant extra meaning for the award_id parameter by specifying it must be the generated_unique_award_id and providing the exact source fields (generated_internal_id from usaspending_search_awards, or generated_unique_award_id from usaspending_get_award). It also clarifies the enum values for type (child_awards, child_idvs, grandchild_awards). This adds value beyond the schema descriptions.

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 clearly states the verb (List), resource (child contracts and task/delivery orders under an IDV award), and the distinguishing feature that each row includes the generated_unique_award_id to chain into usaspending_get_award. It explicitly differentiates from sibling tools like usaspending_get_award (which provides detail on a single award) and usaspending_search_awards (which searches), so an agent can select this tool unambiguously.

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 provides explicit when-to-use guidance: it tells the agent that the award_id must be the generated_unique_award_id of the parent IDV and explains how to obtain it (from usaspending_search_awards generated_internal_id or usaspending_get_award). It also clarifies that IDV category awards from usaspending_get_award have child orders accessible here, effectively telling the agent to use this tool when they have a parent IDV and need child awards. No exclusions are needed because the scope is clearly defined.

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