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

The description is transparent about the side effect ('replacing the current shelves', 'replace existing work'), but this directly contradicts annotations.destructiveHint=false. Since the annotation says the tool is not destructive while the description says it replaces existing work, the agent receives conflicting signals; this is an annotation contradiction.

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 description is front-loaded with the core purpose and the polling handoff to get_background_job, and the confirmation/cost warning is valuable. Minor redundancy ('takes minutes rather than seconds' vs 'takes several minutes'; 'replacing current shelves' vs 'replace existing work') keeps it from being maximally tight.

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 two-parameter tool with no output schema, it supplies the needed execution context: job id for polling, duration, confirmation requirement, cost, and side effects. Missing details are minor, such as an explicit statement that conceit_reshuffle accepts no args and no failure/return shape, but the definition is strong enough for an agent to call and monitor it.

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 already documents both parameters with 100% coverage, and the description adds real meaning to the only kind value by explaining what conceit_reshuffle does, how long it takes, and that args can be omitted when none are needed. It does not further specify the args object shape, which prevents a 5.

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 starts with a specific verb and resource: start a long-running background job and get a job id to poll with get_background_job. It also names the only job kind (conceit_reshuffle) and what it does, making the tool's purpose unambiguous relative to sibling polling/list 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 gives explicit context: use this for work that takes minutes rather than seconds, expect several minutes, and confirm with the user because runs cost money and replace existing work. It does not explicitly point to a non-background alternative such as the closely named sibling reshuffle_conceits, so it stops short of a full when/when-not matrix.

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