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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world behavior, which covers the safety profile. The description's 'deterministic' roughly restates idempotentHint and adds no new behavioral context (no auth requirements, no constraints on what it accepts beyond what the schema already enforces).

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 with no filler. It is efficient, though the brevity is achieved partly by omitting necessary detail rather than by tight writing.

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?

The presence of an output schema relieves the description of explaining return values, but for an 8-parameter tool with 38% schema coverage and no usage or parameter guidance, the description is not complete enough for an agent to invoke it confidently. It also fails to differentiate itself from the many other render/analyze tools.

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 only 38% across 8 parameters, so the description carries a heavy burden and provides none of it. It never mentions the required integer-frequency matrix, the mandatory inputSemantics attestation, the percentage modes, or the label/variable parameters, leaving most parameters undocumented in prose.

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 names a verb ('Render') and a resource ('aggregate crosstab widget'), so the basic action is identifiable, but qualifiers like 'evidence-linked' and 'widget' are vague jargon rather than concrete scope. It does nothing to distinguish this from sibling renderers such as render_table, render_project_table, or the analyzer analyze_crosstab.

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?

There is no guidance on when to choose this tool over analyze_crosstab, render_table, or run_table, nor any stated prerequisite such as needing counts before rendering. The agent must infer usage entirely from the name.

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