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

Annotations are neutral (readOnlyHint=false, idempotentHint=false, destructiveHint=false) and provide no safety profile. The description adds contextual governance details ('enabled', 'owner-curated', 'discovered') but does not disclose potential side effects, authentication requirements, or execution behavior beyond annotations.

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 a single, focused sentence with no redundancy. It conveys the core purpose efficiently and front-loads the essential action.

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?

The description is minimal but the schema and output schema cover parameter details and return structure. However, for a generic gateway tool, an agent would benefit from more context about how discovered servers/tools are identified or how arguments are routed, which the description omits.

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 100%, with all four parameters already described in the input schema. The description adds no additional parameter semantics, so the baseline of 3 applies.

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 states a specific verb ('Call') and resource ('one discovered tool on an enabled, owner-curated downstream MCP server'), which is clear and not a tautology. It distinguishes this tool as a generic gateway to downstream MCP servers, though it does not explicitly contrast it with sibling direct-access tools.

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 no guidance on when to use this tool versus the sibling tools such as github_readonly.get_file_contents or search. There is no mention of when a user should prefer the gateway over direct server tools, nor any exclusions.

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