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

With no annotations provided, the description takes full responsibility for behavioral disclosure. It reveals the output format (JSON with base64 PDF and suggested filename), instructs to decode base64, and states that the PDF is generated in memory and never stored. This covers the key side effects and user-facing 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?

The description is three sentences, each earning its place: main action with default, return/output handling, and alternative for interactive use. No redundancy or filler.

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 simplicity (2 parameters, no nested objects, no output schema), the description covers all essential context: input, output format, how to deliver the result, and an alternative tool. It also compensates for the lack of an output schema by explaining the JSON structure.

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% since both markdown and template have descriptions. The description adds value by noting the default template ('classic') and directing users to list_resume_templates for the full list of 32 ids, which aids parameter selection beyond the schema's enum list.

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's function with a specific verb and resource: 'Render a Markdown resume to a finished PDF using a ResumeMD template.' It distinguishes itself from sibling tools by explicitly referencing list_resume_templates for template IDs and offering an editor alternative.

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 when-to-use guidance: it is for PDF rendering, and explicitly waves off interactive editing, template switching, and color choices to resumemd.pro/editor. It also points users to list_resume_templates for all available template ids, indicating the proper way to choose a template.

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