cueapi-mcp

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

No annotations are provided, so the description carries full burden. It mentions filtering by status but doesn't disclose behavioral traits like pagination behavior (implied by limit/offset but not explained), rate limits, authentication requirements, or what 'cues' represent. For a list operation with 3 parameters and no annotation coverage, this leaves critical operational context unspecified.

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, efficient sentence that front-loads the core purpose ('List cues') and adds the key optional feature ('filtered by status'). There's no wasted wording or redundant information, making it appropriately concise for a straightforward list operation.

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 (3 parameters, no output schema, no annotations), the description is insufficient. It doesn't explain what 'cues' are, how results are structured, pagination behavior, or error conditions. Without annotations or output schema, the description should provide more operational context to be complete for agent 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?

Schema description coverage is 33% (only 'status' has a description), so the description must compensate. It mentions optional filtering by status, which aligns with the schema's enum values, but doesn't explain 'limit' or 'offset' parameters. The description adds minimal value beyond the schema, resulting in a baseline 3 score given the partial 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 clearly states the verb ('List') and resource ('cues on the authenticated account'), making the purpose unambiguous. It distinguishes from siblings like 'cueapi_get_cue' (singular retrieval) and 'cueapi_list_executions' (different resource). However, it doesn't explicitly differentiate from other list operations beyond the resource name, keeping it at 4 rather than 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 provides no guidance on when to use this tool versus alternatives. It doesn't mention when filtering by status is appropriate, how it differs from 'cueapi_list_executions', or any prerequisites like authentication context. With multiple sibling tools available, this lack of comparative guidance 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.