MCP Hub

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

No annotations provided, so description carries full burden. Critically discloses that client_secret is shown only once and must be saved immediately—essential behavioral context for a credential generation tool. Does not mention auth requirements or idempotency, but covers the critical security behavior.

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 structured Args/Returns format that is clear and scannable. Every sentence serves a purpose—either explaining parameters, defaults, or the critical one-time credential warning. Slightly verbose but appropriate given 0% schema coverage.

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?

Excellent completeness given no output schema exists. Describes return structure (Dict with client_id/client_secret) and includes critical security warning. With 5 parameters and complex nested object (metadata), description provides sufficient context for correct invocation.

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%, but description fully compensates by documenting all 5 parameters with clear semantics: comma-separated format for URIs/grant_types/scopes, default values, and examples (e.g., 'My OpenAI GPT'). Adds crucial format details absent from 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?

Specific verb 'Register' and resource 'OAuth 2.1 client' clearly stated. Distinct from siblings like oauth_list_clients (list vs create), oauth_revoke_client (delete vs create), and oauth_get_client_info (read vs write).

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 implied usage context through the Returns section warning ('SAVE THIS - shown only once!'), indicating this is for initial credential generation. However, lacks explicit guidance on when to use this versus sibling tools (e.g., when to register new vs retrieve existing client info).

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