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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond annotations: a cancelled worker cannot publish its file, which tells the agent the consequence of cancellation. It stops short of describing irreversibility or permission requirements.

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 definition is two short sentences, front-loaded with the action and scoped by job state, followed by the key behavioral consequence. Nothing is wasted.

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?

An output schema exists, so return values need not be explained. Still, for a destructive cancellation tool, the description omits parameter meaning for the required job_id and offers no guidance on alternatives, leaving meaningful gaps.

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?

With only 50% schema description coverage, the description must compensate, but it mentions no parameters at all. The required job_id has no description in the schema beyond UUID format/pattern, so the agent gets no natural-language explanation of what identifier to pass; only organization_id is documented in 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?

The description states a specific verb and resource—'Cancel a queued or running Hub export'—making the action unambiguous. It does not distinguish this tool from sibling cancel tools such as cancel_research_analysis or cancel_feasibility_request, leaving differentiation to the agent's inference.

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 implies the applicable conditions by saying 'queued or running,' which is useful context for when cancellation is valid. However, it provides no explicit when-not-to-use guidance and does not mention alternatives for cancelling other research artifacts.

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