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

Annotations already declare a safe read (readOnlyHint=true, destructiveHint=false), lowering the bar. The description still adds useful context: quotes carry share ids for citation, estimatedCompletionTime is a rough upper-bound, and it exposes the fields returned. The archived-response default is only covered in the schema, not here.

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?

It is front-loaded with the core purpose and every clause maps to actual output content, so little is wasted. It is, however, a single dense run-on with nested parentheticals that is heavier than needed.

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?

With an output schema present, the description needn't explain return formatting, and it already covers scope, contents, and onward routing. Nothing an agent needs to invoke it correctly is missing.

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 both params (projectId, includeLowQuality) are fully documented in the schema. The description adds no parameter-specific meaning beyond that, so the baseline of 3 applies.

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+resource ('Deep overview of ONE project') and then enumerates the exact contents: themes with sentiment/recommendations/response counts, average ratings, keywords, quotes with share ids, questions, and estimatedCompletionTime. The 'ONE project' framing cleanly separates it from cross_project_comparison and sibling list 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 explicitly routes the agent onward: use question_breakdown for a full per-question distribution, or get_question for editable detail. That is clear alternative guidance, though it does not state when to prefer this over the likely lighter-weight sibling project_stats.

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