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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses the official CALC+ API source, the specific data fields returned, that rates are ceiling rather than invoiced prices, the exact per-call cost model, and that failed calls are not charged. These are material behavioral details for an agent deciding whether and how to invoke the tool.

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 resource and its contents, then moves to search guidance, an important price caveat, and billing terms. Despite its density, every sentence carries useful information for invoking or interpreting the tool.

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 that an output schema exists and the annotations already signal read-only and open-world behavior, the description covers the remaining essentials: source authority, return contents, search semantics, price interpretation, and payment terms. Nothing critical for correct invocation appears to be missing.

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%, and the schema already documents both vendor and pages, including examples for vendor. The description reinforces that vendor accepts a contractor name or service keyword but adds little beyond the schema and does not clarify the pages parameter.

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?

It names a specific resource, a US federal GSA schedule contractor dossier, and enumerates the exact contents: contracts, labor categories, ceiling prices, statistics, education, experience, and worksite mix. This is clearly distinguishable from generic company-directory siblings such as b2b_manta or b2b_yellowpages.

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?

It says to search by contractor name or a service keyword, which gives basic query guidance. However, it does not explicitly state when to use this tool versus adjacent government-contract tools such as gov_government_contract_awards, gov_sam_gov_wage_determinations, or gov_us_gov_contract_watch.

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