mdshare

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

Annotations indicate read-only, non-destructive, and idempotent behavior, which the description does not contradict. The description adds critical context beyond annotations: the admin URL 'grants full control and is equivalent to a password,' and it should 'never be surfaced to the user unless directly requested,' providing important security and usage insights.

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 front-loaded with the purpose, followed by critical usage guidelines in a structured manner. Every sentence adds essential information—security warnings and explicit usage rules—with zero waste, making it highly efficient and well-organized.

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?

Given the tool's complexity (security-sensitive operation), the description provides complete context: purpose, security implications ('equivalent to a password'), and strict usage guidelines. With annotations covering safety and no output schema needed for a simple retrieval, the description adequately addresses all necessary aspects for an AI agent.

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%, so the schema fully documents the 'document_id' parameter. The description adds minimal semantic value beyond the schema, only implying that the document must be previously uploaded, which is already suggested by the schema's reference to 'upload_markdown response.' Baseline 3 is appropriate as the schema handles parameter documentation.

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 specific action ('Retrieve the admin URL') and resource ('for a document previously uploaded via this MCP server'), distinguishing it from siblings like 'generate_link' or 'list_links' by focusing on administrative control rather than sharing or listing.

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?

Explicit guidelines are provided: call only when user explicitly asks for the admin URL (e.g., 'give me the admin URL'), and do not call for normal upload, share, or collaboration flows. This clearly distinguishes when to use this tool versus alternatives like 'generate_link' for sharing.

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