postmd_get_document_raw

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

Annotations already mark this as readOnlyHint=true; the description adds non-obvious behavioral constraints: no API key required, conditional password handling, and the expired-document failure case. These are important for an agent to know before invoking.

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?

Three short, front-loaded sentences with no filler. Every sentence adds necessary context: what is returned, authentication expectations, and access constraints.

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 read-only tool with two parameters, the description covers purpose, access, and failure conditions sufficiently. It could be slightly more complete by explicitly distinguishing itself from postmd_get_document, but that gap is minor.

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?

The schema documents password but not docCode, and the description reinforces the conditional need for password while implying docCode identifies the document. It does not define docCode's format or origin, so the parameter guidance is adequate but incomplete.

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?

States the exact action and resource: 'Get the stored Markdown source of a document.' The word 'raw' and the focus on Markdown source clearly separate this from the sibling postmd_get_document, which likely returns a processed or rendered form.

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 clear operational context: the tool is public with no API key, password-protected documents require the password parameter, and expired documents cannot be read. It does not explicitly name an alternative or say when not to use it, so it stops short of a 5.

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