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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description goes further by disclosing the snapshot contents and issuing a behavioral directive ('summarise for the reader's role rather than dumping raw JSON'), which meaningfully shapes how the agent should present results.

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 sentences, front-loaded with the payload enumeration followed by the usage directive. No filler; every clause carries information an agent needs.

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 carries the burden of describing returns, and it does so concretely (release counts, issue buckets, run result counts, verification count). Combined with the safety annotations and fully documented params, nothing needed to call 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 description coverage is 100%, and both parameters (botId, projectApiKey) are documented in the schema including the 'Never print it' warning. The description adds no parameter-level detail, so the schema does all the work — the baseline 3 is appropriate.

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+resource (project-wide QA posture snapshot) and enumerates exactly what it aggregates: releases with lifecycleStatus and pass/fail counts, issues by state, activeTestRuns, and testsAwaitingVerificationCount. An agent can distinguish it from narrower siblings like get-release-details or get-suite-execution-stats without opening a schema.

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?

Explicitly names the scenarios: 'weekly QA digests and release-health questions.' That gives clear positive context for selection. It stops short of naming alternatives or exclusions (e.g. when to prefer get-release-details instead), so it falls just under a 5.

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