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 covered. The description adds valuable behavioral context: the tool ranks using keyword, deadline, and applicant-type signals, returns reasons and official records, and is a paid external HTTP endpoint requiring $0.20 USDC via x402.

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 with no filler. The core ranking behavior is front-loaded, and the endpoint, price, and payment method are included because they are essential to invoking this paid 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?

The description includes the endpoint, cost, payment mechanism, ranking signals, and return content, and the schema points to a linked OpenAPI contract for request details. It is reasonably complete for selecting and invoking the tool, though exact request formatting is deferred to external documentation.

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?

The schema declares zero explicit parameters, so the baseline is 4. The description compensates by naming the signal dimensions (keyword, deadline, applicant-type) and the notion of a mission profile, which gives an agent meaningful clues about expected inputs even without a concrete parameter list.

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 and resource: 'Rank current U.S. federal opportunities against a mission profile.' It also distinguishes this tool from sibling search/detail tools by emphasizing fit ranking rather than retrieval or brief generation.

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 intended use is implied by 'Rank current U.S. federal opportunities against a mission profile,' but there is no explicit guidance on when to choose this over federal-grant-search, federal-grant-detail, or federal-grant-shortlist-preflight. No exclusions or alternative conditions are stated.

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