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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds genuinely useful behavioral context by restricting the data exposed to just draft ID and status, excluding other drafts and raw files.

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, front-loaded with the action and the returned scope, with no filler. Every clause earns its place by either defining the output or bounding access.

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 helpfully enumerates what is returned (draft ID and status), which compensates well. The one gap is that it does not explain how the review:prepare token is supplied, given the schema takes no parameters.

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?

There are zero parameters, so the baseline is 4. The description adds no parameter detail because none exist; the only implicit input, the review:prepare token, is not parameterized in 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 (read) and a narrowly scoped resource (the draft ID and status tied to a review:prepare token). The scope phrases 'only' and 'this review:prepare token' clearly separate it from read-heavy sibling tools, though no sibling is named directly.

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?

Usage is implied: call it to inspect the draft associated with a prepare token, and the 'No access to other drafts or raw files' clause sets a negative boundary. However, it never states explicitly when to prefer this over siblings like get_offering or submit_review, nor any prerequisite ordering (e.g., after prepare_review).

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