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

With no annotations, the description carries the full burden. It discloses that this is a write operation, requires the mcp:write scope, and is restricted by ownership and integration permissions. However, it does not describe side effects like whether the write is idempotent, reversible, or what happens on conflict, leaving some behavioral ambiguity.

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?

Three short sentences, no filler. The first sentence immediately states the purpose; the second and third provide essential constraints. Every sentence earns its place.

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?

This is a mutation tool with no annotations and no output schema. While the description covers prerequisites, permissions, and parameter hints, it does not state what happens on success (e.g., returns updated task, returns nothing) or failure. Given the moderate complexity of a two-parameter sync action, this leaves a notable gap for the agent to infer behavior.

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%, so the baseline is 3. The description adds extra semantic value by explaining that task_id should refer to tasks with needs_sync (pointing to poker.game.tasks.list) and that game_id must belong to an imported game. This goes beyond the raw 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 clearly states the tool writes the estimate back to an issue tracker, with concrete examples (Jira story points, Linear estimate). This is a specific verb+resource and is distinct from all sibling tools (no other sync tool exists).

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 explicit prerequisites and exclusions: it only works for imported tasks, only when the integration has write permissions, and only the team owner can use it. It also directs the agent to poker.sources.list to verify permissions, giving clear context for when to invoke. The only missing element is an explicit alternative tool, but no alternative sync tool exists.

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