MCP Hub

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

No annotations provided, so description carries full burden. The 'excluding secret' note is valuable behavioral context indicating sensitive data is filtered. However, lacks disclosure on read-only nature, rate limits, or error conditions.

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?

Uses docstring format (Args/Returns) which is slightly unconventional for MCP but clear. Information is front-loaded and no sentences are wasted. Could condense by removing structural boilerplate.

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 single-parameter lookup tool, covers the basics: purpose, parameter, and return structure. With no output schema, mentioning the Dict return type is helpful. However, with 0% schema coverage, it should ideally elaborate on client_id format or valid values.

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 0%, leaving parameters undocumented. The Args section adds 'Client ID to query' which provides basic semantic context beyond the raw schema. Could be stronger with format requirements or usage examples.

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?

Clearly states the verb (Get) and resource (OAuth client info). Distinguishes from sibling oauth_list_clients by specifying 'specific' client, though could be more explicit about differentiation.

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?

Provides no guidance on when to use this versus oauth_list_clients or other OAuth tools. No prerequisites or conditions mentioned.

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