sheetrender-mcp

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

Annotations cover the safety profile (not read-only, not destructive, not idempotent, closed-world), and the description adds real behavioral context the annotations do not: rows are retained until loaded or 7 days, and the link itself expires after 7 days. It stops short of describing what happens if a link is regenerated or how the link is returned, but the retention/expiry disclosure is substantive.

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?

Purpose is front-loaded, followed by the usage gate, then limits and retention in two short concluding sentences. No filler; every sentence carries distinct information.

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?

An output schema exists, so return values need not be described. For a creation tool the description covers the required ingredients an agent needs: when to invoke, the row cap, and the persistence/expiry window. Nothing material is missing.

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 already documents all three parameters. The description's 'Accepts up to 100 rows' merely restates the schema's maxItems cap and adds no syntax or format detail, so the baseline of 3 applies.

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 ('Create a link to the template's page on the SheetRender website with the user's rows loaded') plus the outcome (kept as a SheetRender project). This is clearly distinguishable from render_documents and list_document_templates without opening any schema.

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 intents (continue on the website, keep/save rows, repeat or schedule the job, email delivery) and closes with 'do not call it otherwise', which is an explicit exclusion. This is the strongest form of when/when-not guidance.

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

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds that it takes no arguments and details the shape of each returned template, which goes beyond what annotations provide; it does not mention error behavior or auth, keeping it at 4.

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 verb and template list, then the workflow guidance. It is dense but almost every clause carries information; the second sentence is long, and some returned-field detail partially duplicates the output schema.

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 zero-argument, read-only discovery tool with an output schema already documenting the return, nothing essential is missing. The description's field-by-field return recap is slightly redundant given the output schema exists, so it lands at 4 rather than 5.

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?

Zero parameters, so the baseline is 4. The description correctly states 'Takes no arguments,' which is consistent with the empty schema, and adds no misleading parameter guidance.

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 (List) and resource (document templates), names the four concrete templates, and enumerates the returned fields. It is instantly distinguishable from render_documents and create_continue_link.

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 says to 'Call this first when the user wants PDFs made from a spreadsheet, a table, a CSV or a list of people' and names the follow-up tool (render_documents) plus the reason (mapping columns onto field keys). This is a full when-to-use plus routing statement.

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

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

With annotations covering only the safe/read-write profile, the description carries the real behavioral load: per-call row cap (25), monthly quota (50 per user/conversation, shared among indistinguishable callers), quota-reset reporting, one-hour link expiry, missing_fields error reporting, and value-type/length rules. That is exactly the context annotations cannot express.

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?

Purpose and usage are front-loaded in the first two sentences, followed by operational detail. It is a dense single block rather than a list, but almost every clause carries actionable information; only minor tightening of the quota sentences is possible.

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?

An output schema exists, so return values need little explanation, yet the description still clarifies the quota portion of the response and error reporting. Combined with limits, expiry, prerequisites and template restrictions, an agent has everything needed to call 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, but the description goes further: it tells the caller to derive keys from list_document_templates, map user columns onto them, pass each row as an object keyed by field key, and states the 2000-character text ceiling and permitted value types. The title/template params get less attention, but the hard part (rows) is well explained.

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 opening sentence gives a precise verb+resource+output: 'Render one PDF per row of data with a built-in template, and return a PNG preview and a PDF download link.' It also names the sibling that supplies inputs (list_document_templates), so the agent can distinguish this from its siblings without opening a schema.

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 trigger conditions are given ('Use when the user has a spreadsheet, table, CSV or list and wants a certificate of completion, letter, donation receipt or job offer letter'), plus an explicit exclusion ('does not accept HTML or custom designs') and the prerequisite step of fetching field keys from list_document_templates.

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