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

Beyond the readOnlyHint annotation, the description discloses important behavior: derived tools are API Evangelist-generated candidates from OpenAPI rather than provider-published servers, and auth-gated servers are reported in coverage.not_enumerable instead of being silently counted as zero. This is substantive behavioral context that affects how an agent interprets results.

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 well-structured and front-loaded: purpose first, then provenance definitions, then filter advice, then a caveat about non-enumerable servers. Every sentence earns its place and there is no filler.

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?

Given there is no output schema, the description does enough to convey what the response contains (tools, operations, auth, provenance, coverage). It could be more explicit about pagination or the required slug parameter, but the core behavior and caveats are covered well.

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 only 40%, so the description carries some burden for explaining parameters. It adds real meaning to provenance by explaining first-party versus derived and warning about interpretation, but it does not explain slug, page, or limit beyond what their names imply.

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 returns every MCP tool a provider ships, along with the wrapped operation and auth, so the agent knows exactly what resource is being fetched. It does not explicitly name siblings like get_provider_operations or find_mcp, but the focus on provider-shipped MCP tools is specific enough to distinguish it.

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 gives concrete usage guidance around the provenance filter, explicitly warning that counting derived tools as the provider's own overstates MCP adoption. It does not name alternative tools or state when to prefer them, but the context for using the tool and interpreting results is clear.

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