api_statusCheck authenticated Cannon Studio account/API connectivity before estimating or creating requests. Requires OAuth or a developer API key; may update key/token usage metadata, but does not spend credits, enqueue jobs, change assets, or expose secrets.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| ok | Yes | ||
| status | Yes | ||
| response | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses that it 'may update key/token usage metadata' but does not spend credits, enqueue jobs, change assets, or expose secrets. This adds behavioral context beyond the annotations, which only indicate readOnlyHint=false. The side effect is noted, though the exact nature of 'usage metadata' is somewhat vague, so a slightly lower score is warranted.
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 two sentences, front-loaded with the primary purpose and directly followed by essential context about prerequisites and non-effects. Every sentence contributes value, with no fluff or repetition.
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 tool with an output schema, the description covers the core purpose, when to use it, required authentication, side effects, and what it does not do. This is complete given the tool's simplicity and the presence of an output schema.
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 tool has zero parameters, and the input schema is empty. The description correctly does not attempt to add parameter information, and the schema coverage is 100% by definition. Baseline score of 4 applies since no compensation is needed.
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 uses a specific verb ('check') and resource ('authenticated Cannon Studio account/API connectivity'), clearly stating what the tool does. It distinguishes itself from sibling tools by specifying it is for use 'before estimating or creating requests,' which sets it apart from estimation and creation 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?
The description explicitly indicates when to use the tool ('before estimating or creating requests') and states the prerequisite (OAuth or developer API key). This provides clear context and implicitly excludes use cases where authentication is not needed or where the user is already past the connectivity-check stage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct resource or action: status, comparison, creation, estimation, fetching, API docs, checkout, generation polling, model availability, pricing, capabilities, offerings, toolkits, workflow recommendation, and knowledge search. Even the get_* and list_* tools have clear, non-overlapping purposes.
Most tools follow a verb_noun pattern (create_generation_request, list_offerings, get_checkout_link), but there are exceptions: api_status is a noun, and fetch and search are single verbs without an object. The mix of get/list/compare/recommend/search/fetch is readable but not perfectly uniform.
15 tools is at the upper bound of the well-scoped range, but each tool serves a clear, distinct purpose in the Cannon Studio domain—from estimation and creation to knowledge retrieval and workflow recommendation. No tool feels redundant or superfluous.
The surface covers creation, estimation, polling, knowledge, and commercial operations, but the generation lifecycle is incomplete: there is no update, cancel, or list tool for generation requests, and the create tool explicitly cannot be cancelled through MCP. This is a notable gap for agents managing ongoing work.