km_add_calculation

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

No annotations provided. Description only states what the action does, not behavioral traits like insertion position, prerequisite of macro existence, or effect on existing actions. Lacks details on return or 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?

Single sentence with an example; no filler. 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 tool among many similar action-adders, it lacks context on where the action is added, ordering, or prerequisites. Minimal information.

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 (100%). Description adds an example for 'expression', clarifying format, but does not significantly enhance meaning beyond 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 the tool adds an action that sets a variable to a calculation result, with an example. It distinguishes from siblings like km_add_set_variable (simple assignment) and km_add_if_calculation (conditional).

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?

Implies usage for calculations like 'Counter + 1', but no explicit when-to-use or when-not-to-use guidance, nor mentions of alternatives among siblings.

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