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

With no annotations, the description carries the full burden and does add meaningful constraints: the caller must be a team member and the assignee must also be a team member. It says nothing about the resulting state (status, whether it's mutable, notifications, or return payload) for a mutation tool, so the disclosure is partial.

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?

Two compact sentences lead with the action and its subject, then append the key constraints. No filler, no restatement of the name, and every clause carries information.

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?

For a 4-parameter mutation tool with no annotations and no output schema, the description covers the permission model and the assignee constraint but omits defaults (e.g., initial status), what happens on success, and any limits. It is adequate but leaves real 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?

Schema description coverage is 50% (team_id and assignee are documented inline). The description adds value by flagging description as optional and adding the 'must be a team member' constraint on assignee that the schema lacks. It still says nothing about title length limits or team_id format beyond the schema's own note.

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 gives a specific verb and resource ('Open a work item on a problem team') and names the key inputs, so the agent knows exactly what will be created. It doesn't differentiate itself from siblings like create_bounty or update_work_item, but the action itself is unambiguous.

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?

'You must be on the team' states a precondition for use, which is genuine usage guidance. However, it offers no guidance on when to choose this over create_bounty or update_work_item, leaving the agent to infer context from sibling names alone.

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