km_manage_variable

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

Description only lists operations (get, set, delete) without disclosing behavioral details such as idempotency, permissions, or side effects. With no annotations, the burden is higher, and the description provides minimal additional insight.

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?

Single sentence is concise and front-loaded with the verb and resource. However, it could benefit from a brief structure explaining each action.

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?

Given the simplicity of the tool and full schema coverage, the description is minimally adequate but lacks reference to sibling tools or clarification of the 'set' action's value requirement, which is already in schema.

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 all parameters with descriptions, so the description adds little extra meaning. The parenthetical in the description mirrors the enum values, offering no new semantic value beyond 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?

Description clearly states tool manages Keyboard Maestro variables and lists supported operations (get, set, delete). However, it does not differentiate from sibling tool km_add_set_variable, which serves a different but related purpose.

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?

No guidance on when to use this tool versus alternatives like km_add_set_variable. The description implies usage for variable management but lacks explicit context for appropriate scenarios.

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