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

Annotations already cover readOnly/idempotent/non-destructive, so 'Read-only' in the description is redundant. However, the description does add genuine behavior beyond the annotations: results are ranked by impact, and the default scope excludes dismissed insights — both are material to interpreting the output.

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?

A single front-loaded sentence that packs scope, content types, ordering, optional filter, and safety profile with zero filler. 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?

With no output schema, the description usefully characterizes the return values (bottleneck/automation/risk/trend insights ranked by impact), which is what an agent needs to decide relevance. The only gap is pagination/limit behavior for a tool that can return up to 100 items.

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 67% and both processId and projectId are already documented in the schema; the description only restates the processId filter. The limit parameter (default 20, max 100) and its interaction with impact ranking are unexplained in both schema and description, so no value is added over the structured fields.

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 resource (Optimize insights for a project) and enumerates the content types returned — bottlenecks, automation opportunities, risks, trends — plus the ranking order. It distinguishes itself from a generic listing by specifying 'Active (non-dismissed)', though it never names the generating sibling run_process_insights.

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 'Active (non-dismissed)' qualifier and 'Optional processId filter' imply this is a retrieval step after insights have been generated, but there is no explicit when-to-use guidance or pointer to run_process_insights as the tool that produces these insights. Usage must be inferred.

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