Tendem MCP

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

With no annotations provided, the description carries the full burden. It discloses that cancellation is possible at any time and notes a financial implication (costs not refunded after approval), which adds useful behavioral context. However, it doesn't cover other critical aspects like permissions needed, whether the action is reversible, error conditions, or rate limits, making it incomplete for a mutation tool.

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 well-structured and concise, with a clear purpose statement followed by usage notes and parameter/return details in separate sections. Every sentence adds value, such as the cost warning, and there's no redundant information. It could be slightly more front-loaded by emphasizing the action first, but overall it's efficient.

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 with financial implications) and no annotations, the description is moderately complete. It covers the purpose, some usage guidelines, and parameter semantics, and an output schema exists, so return values don't need explanation. However, it lacks details on permissions, error handling, and sibling tool differentiation, leaving room for improvement.

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 adds meaningful semantics beyond the input schema, which has 0% description coverage. It specifies that 'task_id' is a 'Tendem task ID (UUID)', clarifying the format and context. Since there's only one parameter and the schema lacks descriptions, this adequately compensates, though it could mention where to find the ID (e.g., from 'list_tasks').

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 ('Cancel') and resource ('a Tendem task'), making the purpose immediately understandable. It doesn't explicitly differentiate from siblings like 'approve_task' or 'create_task', but the action is distinct enough that an agent could infer when to use it versus those alternatives.

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 some usage context with 'Can be called at any time' and the note about costs not being refunded after approval, which implies timing considerations. However, it doesn't explicitly state when to use this tool versus alternatives like 'approve_task' or what happens if a task is already completed/cancelled, leaving gaps in guidance.

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