deactivate_tweak

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

Beyond the destructiveHint annotation, the description adds that deactivated tweaks are prevented from use in new FPE operations, clarifying the behavioral impact. No contradiction with annotations found.

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 with no unnecessary words. The action is stated first, followed by a key consequence and a helpful pointer. Highly efficient and front-loaded.

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 simple state-change tool with two parameters and an output schema, the description covers the purpose, consequence, and parameter discovery. It lacks details on return values or authorization, but the output schema mitigates the former.

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 input schema has 100% coverage, so parameters are already well-described. The description adds no new parameter details beyond referencing 'get_tweak' for the sequence identifier, but this does not enhance the semantic understanding of the parameters themselves.

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 clearly states the verb 'Deactivate' and the resource 'specific version of an FPE tweak'. It distinguishes from sibling tools like 'delete_tweak' and 'deactivate_key' by specifying the exact resource and action.

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?

The description explains that deactivated tweaks cannot be used for new FPE operations, providing consequence. It also explicitly advises using 'get_tweak' to discover the sequence identifier, guiding the agent on parameter acquisition.

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