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

With no annotations, the description carries the full burden and does so well: it discloses the privacy constraint (do not include document text, markdown, DSL source or data values), the cost profile (free, no credits, does not affect renders), and the no-realtime-reply limit. These are exactly the behavioral traits an agent cannot infer elsewhere.

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?

Front-loaded with the purpose and the trigger conditions, then the content rule, then the cost note. It is on the long side for a feedback tool and the four trigger clauses slightly overlap, but every sentence carries actionable information and none is 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?

No annotations and no output schema, so the description must be self-sufficient — and it is. It covers when to call, what to write, what not to include, how to reference a specific render, and what happens after submission. An agent has everything needed to invoke it correctly.

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%, so the baseline is 3; the description adds genuine value by prescribing what `summary` should contain ('what you were trying to do, what you tried, and what you expected') and clarifying how `artifactId` is obtained (from a render call or the X-Artifact-Id header). It does not meaningfully extend the `kind` enum beyond what the schema already defines.

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 a specific verb and resource: report feedback about this MCP server to the makesPDF team, with concrete examples of what counts as feedback. This is trivially distinguishable from every sibling (render_*, validate_*, *_template), which are all document/template operations.

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?

Explicitly enumerates the trigger conditions (a tool failed and you cannot work out why, an error or description contradicted the skill file, a missing capability, a concrete improvement) and adds an exclusion: 'This is not a support channel — nobody replies in real time.' Both when-to-use and when-not-to-use are stated.

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