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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, non-idempotent, closed-world), but the description adds real value beyond them: rendering is deterministic React with 'no paint', and posting is an optional side effect performed after render that returns a post url. It does not mention auth requirements or rate limits, and the side-effectful posting to an external channel sits awkwardly beside openWorldHint=false, but it is not a direct contradiction.

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?

Three short sentences with no filler, front-loading the action and the return values immediately. Slightly clipped phrasing ('no paint') trades a little clarity for brevity, keeping it just under a 5.

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?

An output schema exists, so the description needn't explain return values, and 100% schema coverage handles parameters. What's missing is the routing context an agent needs against seven sibling rendering/posting tools, which leaves the definition adequate but with a clear gap for an 8-parameter tool with a nested body object.

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%, so every parameter is already documented in structured form, and the description only re-states the 'type + body' pairing. Baseline 3 applies because the schema does the heavy lifting and the description adds no format, enum, or constraint detail beyond it.

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 and resource ('Render a Studio data card from a type + body') and names the two required inputs, so the agent knows the core operation. It does not explicitly differentiate itself from siblings like render_asset or studio_automate, which also produce visual output, so it falls short of a 5.

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 never says when to use this tool instead of render_asset, studio_automate, studio_schedule, or post_run, all of which are plausible alternatives in the sibling list. Only an implied scenario ('optional live post after render') is present, with no exclusions or routing guidance.

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