DocuQueue MCP

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

Annotations already indicate this is not read-only (readOnlyHint=false), but the description adds no context about what happens on creation, validation, authentication needs, or side effects. It only restates the high-level purpose, so it does not disclose behavioral traits beyond the annotations.

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 a single short sentence with no wasted words, but it is under-specified. It is concise in length but lacks necessary details, making it borderline appropriate.

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 create operation with 3 parameters and no output schema, this description is inadequate. It does not explain what is required, how to provide HTML content, what response to expect, or any constraints. The description does not provide enough context for an agent to use the tool effectively.

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 0%, and the description does not explain any parameter meanings. It does not mention that html_content is required or what parameters like name and description are used for. The description fails to compensate for the lack of schema descriptions.

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 'Design a new document layout' uses a clear verb ('Design') and resource ('document layout'), which is interpretable as creating a template. It distinguishes from sibling tools like list_templates, preview_template, and fill_template because it implies creation. However, 'document layout' is slightly less specific than 'template', and it could be more explicit.

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 no guidance on when to use this tool versus alternatives. It does not mention preconditions, alternatives, or exclusions. With siblings like fill_template and preview_template, the lack of differentiation makes it unclear when create_template is the right choice.

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 declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is clear. However, the description adds no behavioral context beyond that—no mention of what a 'finished document' means, whether it returns binary data, or any rate limits or authentication requirements.

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 single sentence is concise but under-specified. It does not earn its place because it communicates almost no useful information beyond the tool's name. This is more under-specification than effective conciseness.

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 simple schema but no output schema, the description should at least indicate the tool's role in the job lifecycle (e.g., downloading a completed PDF after fill_template). It also fails to clarify the relationship to sibling tools like get_status or preview_template, making the context incomplete.

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 input schema has one required parameter, job_id, with no description. Schema description coverage is 0%, and the description does not mention job_id at all, leaving the parameter completely unexplained. The description must compensate but fails to do so.

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 'Get your finished document' is vague and does not clearly state the tool's function beyond what the name implies. It uses a generic verb 'Get' without specifying the resource type (PDF) or the context (job completion), and it does not differentiate from sibling tools like preview_template or get_status.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention prerequisites such as having a completed job_id or checking job status with get_status before downloading, nor does it exclude any use cases.

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 declare readOnlyHint, idempotentHint, and destructiveHint: false, providing a clear safety profile. The description adds no extra behavioral context beyond the purpose itself (e.g., that it fetches data from a website), but it does not contradict the annotations. With annotation coverage, a score of 3 is appropriate.

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 a single, concise sentence that front-loads the action ('Extract') and the output elements ('colors, fonts, and logo') and the target ('website'). Every word earns its place; there is no fluff or redundancy.

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?

The tool is simple (one parameter) and has no output schema, but the description implies the return will contain the extracted branding elements. It does not explicitly state return format or error behavior, but for a basic extraction tool with strong annotations, this is largely sufficient. It could be improved by mentioning that the output will contain the extracted items, but that is already implied.

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 defines one required parameter 'website' with no description (0% schema coverage). The description compensates by clarifying that the tool operates on a website, directly implying that the parameter is the URL or website identifier. This bridges the gap and adds meaning beyond the bare schema.

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 begins with a specific verb 'Extract' and identifies a clear resource 'colors, fonts, and logo' from a 'website'. This clearly distinguishes it from sibling tools, which all deal with templates, PDFs, or status. The purpose is unambiguous and actionable.

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 implies usage when one needs branding elements from a website, but it does not state explicit when-to-use conditions or exclusions. It does not mention any alternatives or when not to use it. While the context of sibling tools suggests it is for extracting website branding, the description itself provides no direct 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 indicate this is a mutating operation (readOnlyHint=false). The description adds that PDF generation only occurs after confirmation, which is a valuable behavioral detail. However, it doesn't explain what happens when confirm=false, nor does it disclose any other side effects or requirements, so it's above baseline but not rich.

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 extremely concise: two short sentences with no wasted words. It front-loads the purpose and the key workflow, achieving efficiency without unnecessary verbosity.

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 moderate complexity (6 parameters, no output schema) and sparse annotations, the description is far too brief. It doesn't explain parameter meanings, return values, the confirm default (false), or relationship to sibling tools. The description leaves too many gaps for reliable invocation.

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 has 0% description coverage, so the description must compensate. It gives a vague nod to the confirm parameter ('then confirm') but does not explain any other parameters, including the required template_id and data. This is insufficient for a 6-parameter tool.

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 creates a document and generates a PDF. The verb 'create' and the resource 'document' are specific, and the mention of 'preview first, then confirm' distinguishes it from siblings like create_template. However, it doesn't explicitly mention the template-filling aspect, so it's not a perfect 5.

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 gives an explicit workflow: 'Preview first, then confirm to generate PDF.' This tells the agent to preview before using the confirm flag, which is useful guidance. It implies a sequence but doesn't explicitly state when not to use this tool or mention alternatives by name, so it falls 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.

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds minimal context ('if your document is ready') but doesn't explain what 'ready' means or discuss response behavior. It's consistent with annotations, so not contradictory.

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 extremely short, which is concise, but it's under-specification rather than effective conciseness. It lacks essential details and doesn't earn its place as a useful description for an AI agent.

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?

With no output schema, the description should explain what a status response contains (e.g., states like processing/ready/error). It provides no information about return values, polling behavior, or how to interpret results, leaving the tool incomplete for practical use.

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 input schema includes job_id with no description, and schema description coverage is 0%. The description fails to explain the purpose or format of job_id, leaving the agent without any semantic guidance for this required parameter.

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 clear verb ('check') and resource ('your document'), but ambiguously refers to 'document' rather than the job identified by job_id. It gives a general sense of status checking but doesn't explicitly say 'job status' or distinguish from sibling tools.

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?

No guidance is provided on when to use this tool versus alternatives, when to poll for status, or what conditions warrant calling it. The description doesn't mention any context for usage, such as after submitting a job.

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 declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds no further behavioral context, such as pagination, default sorting, or how 'available' is determined.

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 a single concise sentence with no filler, but it is under-specified. It earns its place as a basic purpose statement but could add useful detail without becoming verbose.

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?

With 3 optional parameters and no output schema, the description is insufficiently complete. It does not explain what the returned list contains or how to narrow results, leaving the agent with too little context.

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 0%, and the description does not mention tags, query, or category parameters. The agent receives no help understanding how these optional filters affect the listing.

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 'Browse available document designs' clearly indicates a listing operation with a specific resource. It distinguishes from siblings like create_template and preview_template by its verb and object, though 'browse' is slightly generic.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention filtering, prerequisites, or scenarios where another tool would be more appropriate.

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 declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is covered. However, the description adds no behavioral context beyond a generic phrase; it doesn't mention that the preview is non-persistent, what formats are supported, or any output details.

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 a single short sentence, which is brief, but it is under-specified rather than effectively concise. It does not convey the necessary information to use the tool, so the brevity is not a positive trait.

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 three parameters including an enum and nested object, and no output schema, the description is far too incomplete. It does not explain what the preview returns, how to use the accept parameter, or what data should look like, leaving significant gaps for an agent.

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 0%, and the description provides no meaning for the three parameters (template_id, data, accept). The description does not explain that template_id identifies which template, data is the fill data, or that accept controls output format. This is a complete failure to compensate for the lack of schema descriptions.

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 'See how your document will look' gives a general sense of previewing, but it doesn't explicitly mention template, data, or rendering. It's not a tautology but is vague and does not distinguish the tool from siblings like fill_template or download_pdf.

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?

No guidance is provided about when to use preview_template versus alternatives. The description does not mention that it's for previewing before filling or downloading, nor does it reference any sibling tools for exclusion.

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