add_effect

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

No annotations are provided, so the description must disclose all behavioral traits. It states the tool modifies the effect chain but omits side effects, required permissions, idempotency, or error conditions.

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?

Two sentences plus a terse code example, front-loaded with the purpose, no redundant text.

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?

Adequately covers target_path usage but lacks explanation of effect_type and return value, even though an output schema exists. Missing cross-reference to sibling 'list_effect_types'.

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 description adds meaning for 'target_path' by explaining its syntax, but 'effect_type' remains unexplained with no enumeration or cross-reference to 'list_effect_types'. Schema description coverage is 0%, so more compensation is expected.

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 a new effect' and specifies the target resource 'bus or event-track effect chain', distinguishing it from siblings like 'remove_effect' or 'bypass_effect'.

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?

Provides explicit format for target_path (e.g., 'bus:/...', 'event:/...'), which guides usage but does not include when-not-to-use or mention of alternative tools like 'set_effect_param' or 'list_effects'.

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