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

With empty annotations, the description discloses key behavioral traits: skipping existing tasks ('Tasks already in the game are skipped'), authorization requirements ('Only the team owner can change a game'), and security scope ('Requires mcp:write scope'). It does not contradict annotations.

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?

Four sentences, front-loaded with the primary purpose, followed by usage modes, behavior, and permissions. Every sentence adds value without redundancy.

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?

Covers purpose, usage modes, permission prerequisites, and idempotency behavior. It could mention what happens when both iteration_ref and query are provided or error handling, but overall it is a strong description for a moderately complex tool.

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?

Though schema coverage is 100%, the description adds the mutual exclusivity relationship between iteration_ref and query, and links iteration_ref to poker.iterations.list, providing extra semantic context beyond the 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 states a specific verb ('Pulls') and resource ('tasks from a connected issue tracker into a poker game'), clearly distinguishing from sibling tools like poker.game.tasks.add by emphasizing the external tracker source.

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?

It indicates when to use it (to import a whole sprint via iteration_ref or search by query) but does not explicitly name alternatives or exclusion rules. The instruction 'Give it either iteration_ref ... or query' provides clear context for invocation.

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