km_add_if_calculation

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

Lacks annotations, and the description fails to disclose behavior such as success/failure outcomes, prerequisites (e.g., macro must exist), or side effects like overwriting existing actions. Only states the action type and condition format.

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 no redundancy, front-loading the verb and resource. However, it could include more context without becoming verbose.

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 simple schema and no output schema, the description is minimally adequate. It fails to mention that the macro must exist or the return behavior, which would be useful for completeness.

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 coverage is 100% with detailed descriptions for thenActionsXml and elseActionsXml, so baseline is 3. The description adds an example for 'calculation' but not for other parameters, providing minimal added 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?

Clearly states the tool adds an If-Then-Else action with a calculation condition, illustrated by an example. Differentiates from sibling 'km_add_if_variable_contains' which uses a different condition type.

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 explicit guidance on when to use this tool over alternatives like km_add_if_variable_contains. Usage is implied but not specified, leaving the agent to infer the appropriate context.

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