calc_contract_rates

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered and the description is not obligated to restate it. The description adds value by disclosing full-result semantics ('all' ceiling rates and 'all' labor categories, not aggregated or filtered). However, it fails to disclose pagination behavior despite a page_size parameter defaulting to 100, which creates ambiguity around how 'all' results are delivered.

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?

Two sentences totaling roughly 30 words, with the primary action front-loaded in the first sentence. There is minor redundancy ('Get all ceiling rates...' vs. 'Shows all labor categories and rates...' both convey the return content), which prevents a perfect score, but the text is otherwise tight and free of 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 low-complexity tool with one required parameter and annotations carrying the safety burden, the description covers the essentials of what the tool returns and the key input. However, with no output schema, the description is the only source of return-structure information, and it gives only a vague sense of the result format; it also leaves the interaction between 'all ceiling rates' and the default page_size of 100 unexplained, which an agent needs to call it correctly at scale.

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 both parameters are already documented with examples ('GS10F0303V', 'GS35F0581X') and defaults. The description echoes the contract number concept but adds no meaning beyond the schema — page_size is not mentioned at all. Baseline 3 applies because the schema does the heavy lifting.

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 names a specific verb ('Get'), resource ('all ceiling rates for a specific GSA MAS contract'), and lookup key ('contract number (IDV PIID)'), making the purpose unambiguous and far beyond a tautology. It also clarifies what is shown ('all labor categories and rates awarded under that contract'). However, it does not differentiate itself from the closely related siblings calc_search_rates and calc_suggest, so it stops short of 5.

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 'for a specific GSA MAS contract by its contract number' implies the tool is appropriate when the caller already knows the IDV PIID, which is useful contextual guidance. Yet there is no explicit mention of when not to use it, nor any pointer to alternatives like calc_search_rates when a contract number is unknown. The usage guidance is implied rather than stated, which leaves sibling routing to inference.

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