Get Subaward

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is well covered. The description adds minimal extra behavioral context beyond the singular result nature, but it does not contradict annotations and does not need to re-explain what annotations already provide.

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 very concise, front-loads the main purpose in the first sentence, and uses a single bullet to fully document the only parameter. There is no filler; the 'Award & Compliance tool' line provides lightweight categorization without bloating the text.

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 lookup with an output schema and strong annotations, the description is nearly complete. It provides the lookup key source and clearly identifies the resource type. It could go slightly further by stating what happens when no report matches, but that is a minor gap given the tool's simplicity.

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 compensate, and it does. The bullet explicitly describes subaward_sam_report_id as a UUID and gives concrete provenance ('from search_subawards or a company's subaward list'), adding real meaning beyond the schema's bare string type.

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 action ('Get') and the specific resource ('one FFATA subaward report') and identifies the exact lookup key ('SAM report ID'). It also distinguishes itself from list-like siblings such as search_subawards by explicitly saying 'one' and by framing it as a retrieval-by-ID operation.

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 for when to use the tool: when you already have a subaward_sam_report_id, and it tells the agent where that ID comes from ('from search_subawards or a company's subaward list'). It does not explicitly state exclusions or when not to use this tool, but the usage context is strong enough for an agent to route correctly.

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