cueapi-mcp

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('Resume') but doesn't explain what resuming entails (e.g., does it restart execution, change status, require specific permissions, or have side effects?). This lack of detail is a significant gap for a mutation tool with zero annotation coverage.

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, clear sentence that directly states the tool's purpose without any unnecessary words. It is front-loaded and efficiently communicates the core action, making it highly concise and well-structured.

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 complexity (a mutation operation with no annotations and no output schema), the description is incomplete. It lacks details on behavioral traits (e.g., what happens when resumed, error conditions, or response format), which are crucial for an AI agent to use it correctly. The high schema coverage doesn't compensate for these gaps.

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 description doesn't add any parameter information beyond what the input schema provides. Since schema description coverage is 100% (the 'cue_id' parameter is well-documented in the schema), the baseline score of 3 is appropriate. No extra value is contributed by the description regarding parameters.

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 action ('Resume') and the target resource ('a previously-paused cue'), which is specific and unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'cueapi_pause_cue' or 'cueapi_get_cue' beyond the obvious action contrast, so it falls short of a perfect score.

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 context by specifying 'previously-paused cue', suggesting it should be used only on cues that are in a paused state. However, it doesn't provide explicit guidance on when to use this versus alternatives like 'cueapi_create_cue' or 'cueapi_delete_cue', nor does it mention prerequisites or exclusions, leaving some ambiguity.

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