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

Annotations declare readOnlyHint=true, destructiveHint=false, etc., indicating safe read-only behavior. The description adds behavioral details: matches department name as case-insensitive substring, uses SCPRS purchase-order data from data.ca.gov, and clarifies it's state-level data. No contradiction 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 two sentences plus an example usage, front-loaded with the core purpose. Every sentence adds value: first sentence states functionality, second adds matching method and data scope. No wasted words.

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 tool with 2 parameters and no output schema, the description is fairly complete: it specifies data source, matching method, and output categories. However, it does not mention pagination, limits, or error handling (e.g., department not found). With no output schema, some return format details would improve completeness.

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 schema already describes both parameters. The description adds the detail that department matching is case-insensitive substring and provides an example fiscal_year format, but these are already in the schema descriptions. Minimal added value beyond the schema.

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 it profiles a California state department's procurement spend, listing specific outputs like total dollars, PO count, top suppliers, and commodity categories. It also gives example queries, distinguishing it from sibling tools like ca_procurement_top_suppliers or ca_procurement_awards.

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 explains what the tool does and provides example questions it answers. It clarifies the data scope (California state, not federal), which helps differentiate from federal-level tools. However, it does not explicitly state when to use this tool versus alternatives like ca_procurement_supplier or ca_procurement_commodities.

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