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

Annotations already cover readOnly/idempotent/destructive, so 'Read only' is largely redundant. However, the warning against re-issuing the action with a fresh requestId is a genuine behavioral instruction about duplicate side effects that the annotations do not convey. It does not explain what the receipt contains or how a failed/in-progress state appears.

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 core sentences are tight and front-loaded. The trailing 'Fields: soclo://tools/soclo_ads_operation_status' is an unexplained URI fragment that reads like an internal reference and costs clarity rather than adding it.

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 agent gets no description of what a receipt actually returns (status fields, success/failure indicators). The URI pointer may hold that information, but as written the description leaves the return shape opaque for a recovery-critical 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?

Only one parameter with 0% schema description coverage, and the schema gives just a bare string. The description implies requestId is the id from the earlier uncertain action, which is useful, but it adds no format, source, or lookup-failure semantics beyond that hint.

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+resource: read the original requestId receipt for an ad action. This is clearly distinct from the many mutation siblings like soclo_ads_create_* or soclo_ads_update_*. It never explicitly contrasts with analogous receipts like soclo_leads_op_status or soclo_creators_op_status, so it stops 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?

Gives a concrete trigger — 'after an uncertain ad action' — plus an operational rule ('never buy the same action again with a fresh requestId'). That is real when-to-use guidance. It does not name an alternative tool or state what to do if the receipt is missing, keeping it below 5.

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