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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that the result is a link to the rendered analysis, but says nothing about link lifetime, whether it is shareable, or what the payload looks like; 'keep self-serving' is opaque and conveys no behavioral trait.

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 short sentences with the purpose front-loaded, which is efficient. However, 'keep self-serving' is a confusing, apparently malformed clause that occupies space without conveying anything actionable, weakening an otherwise tight description.

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?

There is no output schema, and the description states the return is a link, which is the key fact an agent needs. But it omits link expiration, shareability, and error behavior when the referenced analysis does not exist, leaving some gaps for a tool that bridges to an external app.

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 50% (name is documented, params is not), so the description usefully compensates by instructing to 'pass the same name/params you used for the analysis', which establishes that params must mirror the earlier analysis call. That is meaningful semantics beyond the schema's bare 'additionalProperties: {}' object.

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: 'Get a Quattr app link' whose purpose is viewing the 'full rendered analysis'. This is a clear read-oriented purpose, though the garbled phrase 'keep self-serving' muddies intent and the description never distinguishes this from the sibling render_analysis, which appears to produce the analysis this link points to.

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?

'Pass the same name/params you used for the analysis' is genuine usage guidance about how to invoke it, implying the link corresponds to a previously-rendered analysis. However, it gives no explicit when-to-use versus render_analysis, summarize_results, or run_dashboard, so selection between siblings remains inferred.

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