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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is covered externally. The description contributes real value by disclosing the return payload ('rate records plus full aggregation statistics'), but says nothing about pagination defaults (page_size=100), ordering behavior, or result-size limits for what could be a very large scan.

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?

Three short sentences with the scoping rule front-loaded and the use case in the middle. Efficient, though the embedded example is verbose relative to the thin coverage it delivers on parameters.

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?

An output schema exists, so return values need not be explained. But for a 13-parameter tool with 0% schema description coverage and no annotations on parameter behavior, the description is far too thin — an agent still cannot tell what most filters accept, what the enum codes mean, or how ordering interacts with sort.

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 coverage is 0% across 13 parameters, so the description must carry the burden and it does not. The example obliquely hints at education_level and experience_min/max filters, but sin, worksite, price_min/max, business_size, security_clearance, sort, ordering, page and page_size get no explanation whatsoever, and the S/O business_size enum is never decoded.

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?

States a specific verb and resource ('Browse rates') and immediately narrows scope with 'filters only (no search keyword)', which implicitly steers the agent away from keyword_search and exact_search. It stops short of naming a sibling explicitly, but the action and the boundary are both unmistakable.

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?

Offers one concrete use case ('market segment statistics: what do all BA-level rates with 5-15 years experience look like across all of GSA MAS?'), which is genuinely illustrative. However, it gives no explicit when-not guidance, no statement of prerequisites, and never names which alternative to reach for when a keyword is involved beyond the parenthetical.

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