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

Annotations already include readOnlyHint=true, and the description adds meaningful behavior: it returns a synthesized view across all OpenAPIs, exposes extra fields only when agentic-access is published, and explains that the context parameter is never included in results or used for ranking. This goes beyond the annotation without contradicting it.

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 longer than average but every clause carries information: the first sentence enumerates output fields and scope, the second explains the agentic-safety filtering use case and the context parameter's behavior. It is front-loaded and structured, though it could be tightened without losing meaning.

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, the description compensates by listing the returned fields and explaining the conditional agentic-access fields. It covers the tool's main purpose, filtering options, and safety guidance. Pagination behavior is not described beyond the schema's limit range, but page is standard and the rest is adequately covered.

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 70%, and the description adds semantic value by explaining consequence as 'read vs something that moves money' and action_class as 'agentic action class', which clarifies filtering intent. It also explains the purpose of context more deeply than the schema. Some parameters like slug and page remain minimally described, but the main filtering parameters are clear.

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 the tool lists every operation a provider exposes across all OpenAPIs, with specific output fields (method, path, operationId, summary, API, deprecation). It positions itself as the shortcut for 'what can I actually call here?', which differentiates it from narrower siblings like deprecated_operations or per-API lookups.

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 explicitly identifies when to use it: when you want the full surface of callable operations across all of a provider's specs without fetching and parsing each one. It also advises filtering by consequence/action_class to find the safe surface before agent use, but it does not name specific sibling tools or state when not to use it.

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