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

readOnlyHint=true already covers the safety profile, so the description's added value is the concrete transport detail (GET /api/v0/prospects) and the return envelope shape { meta, response } — both genuinely useful for an agent. It stops short of mentioning auth, rate limits, or result-size caps beyond the schema.

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, front-loaded with identity, then endpoint, then capabilities and return shape. Nothing is padded and no sentence is filler for an agent that needs to decide and call.

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?

With no output schema, mentioning the { meta, response } envelope is a real contribution, and pagination/field/filter support is disclosed. Only the absence of any auth, limit, or result-count caveat keeps this from being fully complete.

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 every parameter already has a detailed description, so the schema carries the load. The description merely lists the same parameter names with no added syntax or semantics, which is the baseline case.

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 ('List prospects') and even defines the domain entity as 'sales opportunities in the pipeline', plus names the underlying endpoint. It does not explicitly route the agent against the singular get_prospect sibling, so it falls just short of the top tier.

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 only enumerates supported query mechanics (_page/_limit/_fields/_filters/_search); it never says when to use this list tool versus get_prospect or the other list_* siblings, and gives no exclusions or scoping advice.

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