Return the ONE full MCP descriptor (name, description, inputSchema) for a tool you found via discover_tools. Then run it with tools/call.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | exact tool name |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds minimal extra context (returning a descriptor), but does not contradict 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 one sentence with two clear parts, no wasted words, and front-loaded with the core action. It is concise and well-structured.
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 simple tool with one parameter and full annotations, the description covers the entire workflow: discovery, schema retrieval, and subsequent call. No output schema is needed for this read-only operation.
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% and the parameter description ('exact tool name') is already in the schema. The description adds no additional meaning 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?
The description clearly states the tool returns 'the ONE full MCP descriptor' for a specific tool, using the verb 'return' and specifying the resource. It distinguishes itself from sibling tools by linking to the discovery workflow.
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 provides clear context: use after 'discover_tools' and before running with 'tools/call'. It implies a sequence and differentiates from siblings by workflow stage, though it doesn't explicitly state when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Many tools serve similar purposes (e.g., web_read vs browse_read, web_discover vs browse_discover, research vs web_search + browse). Descriptions help differentiate, but the overlap is notable.
Most tools use a consistent verb_noun snake_case pattern (e.g., archive_message, browse_navigate). Minor deviations like standalone 'browse' and 'identity' are acceptable.
57 tools is very high for a single server, even with discover_tools. The broad domain coverage does not justify the count; it feels overloaded.
Covers identity, memory, browsing, human tasks, errands, messaging, and research comprehensively. Minor gaps might exist (e.g., no explicit agent-to-agent contract tools), but core workflows are well-supported.