restore_assumption

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

Discloses key behaviors: creates new model version, restores assumption to active, control group structure unchanged, re-attestation required. With no annotations, the description carries the full burden and covers important side effects.

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?

Four sentences, each earning its place: purpose + versioning side effect, status change, control group behavior, re-attestation requirement. No fluff.

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?

All necessary context provided given the tool's complexity: mutation side effects, control implications, attestation requirement. Output schema exists so return format is covered.

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 covers 2 of 3 parameters with descriptions (model_id, assumption_id). Description adds no further parameter details. The undocumented server_version parameter lacks guidance, but overall schema coverage at 67% provides adequate baseline.

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?

Clearly states 'restore a soft-deleted assumption' and notes it creates a new model version. Distinguishes from sibling tools like 'remove_assumption' which soft-deletes and 'edit_assumption' which modifies.

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?

Provides context that the assumption returns to active status, control groups remain intact, and re-attestation is required. However, does not explicitly state when to use this tool versus alternatives or when not to use it.

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