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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false; 'Read only' merely restates them and earns no credit. Nothing is added about whether the state resolves to queued/running/done/failed, whether to poll, or what an agent should expect mid-flight — real gaps for an async operation tool with no output schema.

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 core action, no filler. The trailing 'Read only' is a small redundancy against the annotations rather than a structural flaw.

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?

A single-parameter tool with full schema coverage, so the call itself is unambiguous. However, with no output schema the description should say what 'state' looks like (status values, results location, error cases); that is the one substantive omission.

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 coverage is 100% and the opId field description ('The operation id returned by search or pitch') already carries the meaning, so the baseline of 3 applies. The description adds no syntax, format, or lifecycle notes beyond 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?

Uses a specific verb ('Read the state') plus a scoped resource ('a search or pitch operation'), which tells an agent this is the status-check counterpart to soclo_creators_search and soclo_creators_pitch. It stops short of naming those sibling tools, so the differentiation is implied rather than explicit.

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 phrase 'a search or pitch operation' implies you call this after kicking off one of those, but the description never says when to poll, how often, or what to do when the operation reaches a terminal state. Only the schema's opId note ('returned by search or pitch') reinforces the sequencing.

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