add_effect

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

The description implies a mutation (adding an effect) but fails to disclose behavioral details such as side effects, permission requirements, or state changes. With no annotations, the description should provide more transparency about what happens when the tool is used.

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 very concise, using only four words. While it is front-loaded and straightforward, it may be overly terse. Given the simplicity of the tool, this conciseness is acceptable, but a little more context could improve it without losing efficiency.

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?

Considering the absence of annotations, output schema, and nested objects, the description is too brief to provide complete context. It does not explain the effect of adding an effect, valid values, or what happens to the pattern, leaving significant gaps for an AI agent.

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% description coverage for both parameters ('effect' and 'params'). The description 'Add effect to pattern' does not add further meaning beyond what the schema already provides, so a baseline score of 3 is appropriate.

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 'Add effect' and the target 'pattern', effectively conveying the tool's purpose. It distinguishes from its sibling 'remove_effect'. However, it lacks specificity about what constitutes an effect or which pattern is modified, leaving some ambiguity.

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 is provided on when to use this tool versus alternatives like 'remove_effect' or other effect-related tools. There are no conditions, prerequisites, or context for usage, making it difficult for an AI agent to decide when to invoke this tool.

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