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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered externally. The description adds only the format/serialization context; it says nothing about output size, pagination, or whether all endpoints are guaranteed included, which would matter for large collections.

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 short sentences, front-loaded with the action and formats. Nothing is redundant or buried, though the second sentence is more sales pitch than spec.

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?

A simple read-only, two-parameter tool with full schema coverage and no output schema; the essentials are present. Only minor gaps remain around output characteristics (size/limits) for very large collections.

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 the format parameter already documents the enum, its default, and the spec versions. The description merely repeats that OpenAPI 3.1 or Postman 2.1 is chosen, adding no syntax or behavior beyond the schema.

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 (export) and resource (an API collection) plus the two output document formats, so an agent can distinguish it from get_api_collection or list_api_collections. It stops short of explicitly contrasting with those siblings, but the scope is unambiguous.

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?

"Handy to read the whole API at once" gives an implied use case (want a full picture rather than browsing endpoints), but it never says when to prefer this over get_api_collection or when not to use it, and names no alternative.

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