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 show destructiveHint=false and readOnlyHint=false (which means likely a normal write operation). The description doesn't add behavioral context - no mention of whether the deck is saved, returned, or rendered, or any side effects. The phrase 'Generate' implies creation, but without elaboration on the output behavior, the agent may be uncertain what happens to the generated deck.

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?

One concise sentence that front-loads the core action. The phrase 'from templates and data' is slightly vague but not wasted. Efficient use of limited space.

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?

Missing critical context: given 10 sibling tools, the agent needs to know how this differs from fill_template (which likely fills a single template) and save_deck (which likely saves a deck). No mention of what the output is used for, whether it creates a new deck or modifies an existing one, or any prerequisites. The schema describes the input shape but not the tool's purpose within the broader workflow.

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% - the schema documents the single 'slides' parameter with its nested structure and template options. The description doesn't add any parameter-level detail beyond what the schema already provides, which is acceptable given the coverage.

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+resource ('Generate a presentation deck') but lacks specificity about what 'from templates and data' means in practice - it doesn't distinguish from sibling tools like fill_template or save_deck. The resource is ambiguous ('deck' could mean any presentation).

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?

Implied usage - generating a deck from templates and data - but no explicit context on when to use this instead of fill_template, preview_template, or save_deck. No exclusions or alternatives mentioned despite having 10 siblings, which is a significant gap.

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 declare openWorldHint=true, idempotentHint=false, and destructiveHint=false, but the description adds meaningful behavioral context: the tool generates visualizations and decks, implying non-deterministic output (due to research) and no destructive side effects. However, it does not disclose specifics like data sources, error handling, or if multiple calls yield different results, which would further clarify behavior beyond 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, concise sentence that clearly states the tool's purpose. Every word is necessary—no filler or redundancy. It is front-loaded with the key verbs and resource, making it easy to scan.

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 has 2 parameters (both simple types), no output schema, and moderate annotations, the description is adequate but not complete. It covers the core purpose and parameter hints, but lacks details on output structure, behavior with different formats, or edge cases (e.g., empty topic). The presence of sibling tools suggests more guidance would help the agent select 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 description coverage is 50%, so the description partially compensates. The 'topic' parameter is explained in the schema as 'What to research and visualize', which aligns with the description. The 'format' parameter is documented only via an enum, but the description's mention of 'visual deck' and 'charts and visualizations' hints at output style. Still, the description could explicitly describe each parameter's role to fully compensate for the coverage gap.

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 purpose: 'Research a topic and generate a visual deck with charts and visualizations.' It uses a specific verb ('Research' and 'generate') and names the resource ('visual deck'). However, it does not differentiate from siblings like 'create_template' or 'save_deck', which could overlap in function, so it loses a point.

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. Given the siblings (like 'fill_template', 'preview_template', or 'save_deck'), there is no explicit context for selecting this tool, nor any mention of prerequisites or exclusions.

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?

The annotations already cover the safety profile with readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds that the output includes field schemas, which is useful context, but it does not disclose any other behavioral details such as authentication requirements, pagination, or return shape.

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, front-loaded sentence with no filler. Every word earns its place: it names the action, the resource, and the notable output detail.

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-parameter, read-only, idempotent listing operation, the description plus annotations provide everything needed to invoke the tool correctly. It names the return detail ('field schemas'), and the lack of side effects is already declared by annotations.

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?

There are zero parameters, so the description does not need to elaborate on input semantics. The empty input schema is sufficient, and the baseline of 4 applies because no parameter documentation burden exists.

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 specific verb and resource: 'List available deck templates'. It also adds that the list includes field schemas, which clarifies the output. However, it does not distinguish itself from the similarly named sibling tool list_templates, so it stops short of a full 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?

No guidance is given about when to use this tool versus similar sibling tools such as list_templates, preview_template, or create_template. An agent must infer the right choice from the name alone, and the description does not mention any exclusions or alternatives.

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.

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false. The description adds that the tool 'save's and produces a shareable URL, which confirms a write operation with a side effect (persisting the deck). However, it does not disclose whether the tool overwrites existing decks, requires authentication, or how the URL is scoped (e.g., public vs. private). With annotations already hinting at non-destructive but non-idempotent behavior, the description adds modest clarity about the result but lacks deeper behavioral context.

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 sentence that efficiently states the action and the outcome. Every word adds value; there is no fluff. It could be slightly more structured (e.g., front-loading the action more clearly), but it is appropriately sized for a two-parameter tool with no 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?

Given the tool's moderate complexity (2 required params, no output schema, no nested objects), the description is somewhat incomplete. It does not explain return format (e.g., the structure of the URL), error conditions (e.g., invalid HTML), or whether the deck is publicly accessible. With annotations providing limited behavioral hints, the description leaves gaps for an AI agent to infer 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% (both 'html' and 'title' are described with basic descriptions). The description does not add new meaning beyond 'HTML content to host' and 'Title for the document.' It does not clarify edge cases like required format for HTML, allowed characters in title, or size limits. Since schema already covers what the parameters are, a baseline of 3 is appropriate.

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 a specific action ('save a presentation deck') and the main outcome ('get a shareable URL'). It distinguishes itself from siblings like 'create_template' (which creates a reusable template, not a deck) and 'download_pdf' (which downloads, not saves). However, it could be slightly more precise about what 'save' entails versus just hosting the HTML as an intermediary step.

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 for saving/publishing a deck and getting a URL, but it does not explicitly state when to use this versus alternatives like 'fill_template' (which uses a template to generate HTML) or 'create_template' (which creates a reusable template). There is no guidance on prerequisites (e.g., HTML already generated from a template) or when NOT to use it.

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