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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds one genuine behavioral fact beyond them — that respondent rows are never included — but says nothing about error behavior for non-succeeded jobs or the shape of the rendered widget.

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 tight sentences, front-loaded with the operation and scope. Every clause earns its place, including the respondent-row exclusion.

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 the return value; it partially does so (aggregate result rendered as a widget, respondents excluded) but omits format and completion/failure semantics. Adequate but with clear gaps for a render step.

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 50%; workspaceToken is fully documented in the schema (secret capability, never in query string) and jobId is a self-evident UUID. The description clarifies that jobId refers to a render_project_table job, which adds marginal meaning, but does not document jobId's provenance or any constraints beyond the schema.

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 (render) and resource (canonical aggregate result) and ties it to the output of a succeeded render_project_table job, which usefully distinguishes it from the sibling that creates the job. It does not, however, explicitly contrast itself with other render_* or get_job siblings.

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 phrase 'succeeded render_project_table job' implies a prerequisite and a lifecycle position, so usage is inferable. But there is no explicit when-to-use/when-not guidance and no named alternative (get_job, render_table, render_crosstab), leaving the agent to infer the routing.

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