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

Annotations already declare read-only, idempotent, non-destructive, and closed-world, so the bar is lower, yet the description adds real value: a hard page limit of 50 providers, disclosure that public consented outcome context is kept separate from ratings, and that missing data is treated as unknown. These are behavioral facts not present in the 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?

Three sentences, front-loaded with the core ranking action, then pagination and data caveats. Compact and mostly waste-free, though the outcome-context sentence is a bit cryptic without more grounding.

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 needn't be explained, and annotations cover the safety profile. However, for a matching tool whose four parameters have 0% schema coverage, the description leaves industry/geography/demandId semantics unexplained, which an agent needs to call it correctly.

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 0%, so the description must carry all meaning for the four parameters, yet it only loosely gestures at cursor pagination (calling it 'nextCursor' while the actual param is 'cursor'). It never explains demandId, industry, or geography, leaving the filter parameters undocumented in both schema and description.

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: ranks published providers by declared skill labels and market fit. This distinguishes it in spirit from browse_service_providers (browsing vs. match-ranking), but it never names a sibling to make the distinction explicit.

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?

Provides pagination guidance ('Use nextCursor for more candidates') and a data-quality caveat, but gives no explicit when-to-use guidance versus siblings like browse_service_providers or browse_owner_demands. Usage is implied by the description rather than stated as selection criteria.

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