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

Annotations cover the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false), and the description adds genuinely non-obvious behavior: this is asynchronous, it enqueues a hosted job, and the result must be fetched via get_job. It omits auth/permission requirements and how to handle a failed job, but the async contract is the key disclosure an agent needs.

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 with the primary action front-loaded and the follow-up routing placed second where it belongs. No wasted words, though the second sentence is compressed to the point of obscuring the parameter contract.

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?

For a 7-parameter write tool with no output schema and 29% parameter coverage, the description is too thin: it never explains the revision-binding semantics, the workspaceToken/evidenceId roles, or what the queued job ultimately returns. Only the async hand-off to get_job is covered, leaving most of the invocation contract undocumented.

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 29% (only requestId and workspaceToken are documented), so the description is expected to compensate and it does nothing — no mention of projectId, tableId, expectedRevision, evidenceId, or waveId. The revision/evidence pair is especially opaque and is left entirely unexplained.

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 (project table), scoped as a 'revision-bound saved table execution,' which distinguishes it from render_crosstab and run_table. The phrase 'canonical workspace evidence widget' is internal jargon that adds no discriminating information, but the core purpose is clear.

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 description implies usage via the async workflow ('Queues a hosted job; use get_job to retrieve its result'), which routes the agent correctly to a sibling for the result. However, it never states when to prefer this over render_crosstab, run_table, or run_tab_book — the closest alternatives — so selection depends on inference.

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