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

Without annotations, the description carries the full burden and does so thoroughly. It discloses that nothing is uploaded, the link itself is the document, anyone holding it can read it, and it imposes clear privacy/safety constraints: ask first, no secrets, no personal data, no confidential material, and a ~100 KB limit.

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?

Every sentence earns its place. The description front-loads the core action, then adds output handling, privacy implications, consent requirements, and size constraints with no filler or repetition.

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 tool with only two simple parameters and no output schema, the description is complete enough: it covers input, output behavior, confidentiality, user consent, and a practical size limit. An agent can confidently decide when and how to invoke it.

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 baseline is 3. The description adds valuable context beyond the schema by stating the markdown size limit and clarifying the output link behavior, though it does not deeply elaborate on the title parameter beyond what the schema already says.

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 action and resource: 'Render markdown as a typeset, paginated document at a Magzdown URL' and clarifies the output is a link. It clearly distinguishes what the tool does even without sibling tools to compare against.

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 explicitly tells the agent how to present the result ('hand it to the user as a markdown link instead of pasting the raw markdown'), when to ask the user for permission, and what content should never be encoded. There are no sibling tools, so an alternative-selection rule is not needed.

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