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

Goes beyond the destructiveHint annotation by disclosing immediate execution and possible vendor workflow side effects, plus the 'projects.create' permission requirement. It stops short of describing failure behavior or irreversibility, so not a 5.

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, front-loaded with the action and scope, then permission, confirmation, and side-effect notes. No wasted text.

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 destructive mutation with no output schema, it covers permissions, user confirmation, and downstream effects. The remaining gap is the undocumented parameter semantics, which the description does not backfill.

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 only 33% across 6 parameters with nested objects, and the description adds no meaning for projectStatus, estimatedValue, projectName, or the employee-reference objects. It only alludes to clientOpportunityId via 'existing client opportunity'.

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?

States a specific verb and resource ('Create a project') plus its required parent ('attached to an existing client opportunity'), which cleanly separates it from the sibling read/update/list project tools.

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 implies the prerequisite (an existing client opportunity) and adds a confirmation workflow ('Show the exact fields to the user before calling'), but it never names alternatives or says when not to use it versus update_project or get_project.

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