truth_logout

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

Annotations already indicate destructiveness and non-read-only, but the description adds specific context about what is destroyed (the locally stored Keychain token) and that explicit confirmation is required. This goes beyond the structured fields, although it doesn't detail potential side effects beyond token deletion.

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 a single, front-loaded sentence with no wasted words. It efficiently conveys the action, the target, and the confirmation prerequisite.

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, single-parameter destructive tool with rich annotations and an output schema, the description is complete. It covers the operation scope and the confirmation requirement, leaving no significant gaps for an agent to select and invoke the tool correctly.

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 has 0% description coverage, so the description must compensate. It does by stating 'Requires explicit confirmation,' which directly explains the meaning and purpose of the 'confirm' parameter (must be true). This adds semantic value beyond the schema's 'const: true' constraint.

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 action ('Delete') and the target ('locally stored Truth Social token from Keychain'), which is specific and distinguishable from all sibling tools that perform read or search operations. It fully clarifies what the tool does.

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 implies the tool is for logging out by deleting the local token and explicitly notes that explicit confirmation is required. While it doesn't mention alternatives or exclusions, the context is clear because no other sibling tool handles logout, and the confirmation requirement is a key usage condition.

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