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

Beyond the readOnly/idempotent annotations, the description adds meaningful behavioral context: proposal state versus work state, what done means, and how readyToRead should be interpreted. This is valuable nuance for a status-reading tool, though it is not exhaustive about all response semantics.

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?

The purpose is front-loaded, but the description is dense and somewhat repetitive, especially around proposal state versus work state. Several sentences are useful, but the same distinction is restated in ways that could confuse rather than clarify.

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?

The output schema exists, so return-value documentation is not required. The description covers the key conceptual distinction and actionId sourcing, making it largely complete for this tool despite some unclear phrasing.

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 schema only describes workspaceId, leaving actionId undocumented in the schema. The description compensates by explaining that actionId may be a proposal actionId, a work handle, or an actionId from readWaitingItems, which materially helps parameter selection.

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?

The description clearly states that the tool reads the current status of one proposal or queued work item and lists the possible states. It distinguishes proposal state from work state, though the phrasing is somewhat tangled and could be sharper against sibling tools.

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?

It explains where the required actionId can come from, including proposals and readWaitingItems, which gives useful invocation context. However, it does not explicitly say when to use this tool versus readWaitingItems or other read tools.

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