list_mcp_servers

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuine context beyond that: pagination behavior ('one page at a time') and the OAuth token requirement, both of which the annotations do not convey.

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?

Four short sentences, with the core purpose front-loaded ahead of the routing hints and the auth prerequisite. No filler and no repetition of schema or annotation content beyond what adds value.

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?

For a two-parameter paginated list tool with full schema coverage and an output schema absent, the description covers purpose, alternatives, pagination, and the auth requirement. Nothing critical for correct invocation is missing, though it says nothing about what a page contains or total counts.

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 pageToken's description ('Page token from a previous list response. Omit it to read the first page.') is already fully documented in the schema. The description's 'one page at a time' phrasing only loosely echoes this, adding no syntax or format detail beyond the schema baseline.

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+resource+scope: 'List MCP servers registered in one environment, one page at a time.' It explicitly names the two closest siblings (register_mcp_server for adding, update_mcp_server for changing), so an agent can distinguish intent without opening any schema.

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?

Routes the agent to the right alternative for add/change operations, which is the main selection decision for this family. It does not cover when this list would be preferred over related list tools, but for a CRUD-list tool the guidance is clear and actionable.

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