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

The annotations declare readOnlyHint=false and destructiveHint=true, while the description frames the operation as a 'status read' that 'requests' a provider observation; 'request' softens this into a write-request reading, but the defensive nuance is never explained, which is a notable gap given the destructive hint. What the description does add beyond annotations is genuinely useful: 'Pending/running is not completed product delivery; counts and errors remain provider observations' warns the agent not to treat in-flight results as delivered counts. Auth/permission needs and request lifecycle are still undisclosed.

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 sentences, front-loaded with the action, no filler. The second sentence is dense but earns its place as an interpretation caveat; a slightly clearer separation of purpose vs. caution would improve readability without lengthening 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?

For a 6-parameter tool with a nested request object, a required request_key, a work_id linkage, and a destructive annotation, two sentences are thin; an output schema covers return shape, but the multi-step sync flow (request → check → stop/recover/apply) and the role of request_key idempotency are unexplained. An agent could invoke it but has little basis for placing it correctly in a catalog-sync workflow.

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 description coverage is only 50% and the description adds no parameter meaning at all: work_id, request_key, and the nested arguments.request fields (operationId, storeId, accountId, action, syncId) are undocumented in prose. The two parameters that do carry schema descriptions (read_skills, expected_catalog_version) are left entirely to the schema, so the description does not compensate for the coverage gap.

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 and resource: 'Request one current provider status read for a native catalog sync.' That is clearly distinguishable from a generic catalog listing, but the description does not differentiate it from the crowded catalog-sync family (native.genads_catalog_sync_request, native.genads_catalog_syncs, native.genads_catalog_sync_review, native.genads_apply_catalog_sync), which share near-identical framing.

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?

There is no when-to-use guidance, no prerequisites, and no named alternative. It never says whether this is the first step of a sync flow, whether it should be polled or repeated, or how it relates to stop/recover siblings. The only guidance is about interpreting the result, not about choosing the tool.

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