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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint, so the added "Read-only" is largely redundant. The description does add that it reads a *draft* with *open questions* and *approval state*, which hints at the mutable workflow state being observed, but it discloses no further traits such as what happens when no plan exists.

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 compact sentences with the action and scope front-loaded and the read-only guarantee appended. Every clause carries information about what is retrieved; there is no filler or repetition.

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 return content, and it does so by enumerating the draft, open questions, approval state and review link. What is missing is edge-case behavior (e.g., no plan yet, not connected), a small gap for a state-reading tool.

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?

The tool takes zero parameters, so the schema baseline is 4 by rule. Nothing in the description needs to explain parameter syntax, and it correctly adds no spurious parameter guidance, though it also cannot add meaning where none exists.

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 ("Reads") and resource ("conversion plan") and further enumerates the scope of what is read: the draft, open questions, approval state and review link. This distinguishes it functionally from the approve/propose siblings, but it never names those siblings or explicitly contrasts itself with them, so sibling differentiation is implicit rather than stated.

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 word "current" and the emphasis on draft/approval state imply this is the inspection step before acting via approve_conversion_plan or approve_and_start_conversion_plan, giving implied workflow guidance. However, there is no explicit when-to-use statement, no named alternative, and no exclusions, so the agent must infer the routing.

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