romaco_remove_indicator

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

Discloses that removal is by type, case-insensitive, and removes the first matching indicator if multiple exist. No annotations are provided, so the description carries the burden; it adequately covers key behavioral traits, though could mention side effects or error cases.

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, no fluff. Essential information is front-loaded: the action and a usage hint. Every word earns its place.

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 (one param, no output schema), the description is fairly complete. It explains what the tool does and how to check active indicators. Could mention behavior when no indicator of the given type exists, but not required.

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% coverage with a description for indicatorType. The description adds meaning: 'Case-insensitive. Removes the first matching indicator if multiple exist,' which goes beyond the schema's basic description.

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 action: 'Remove a technical indicator from the chart by type.' The verb 'remove' and resource 'technical indicator' are specific, and 'by type' distinguishes it from siblings like 'romaco_add_indicator' or 'romaco_remove_alert'.

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 clear context by referencing 'romaco_get_chart_context' to see active indicators before removal. Does not explicitly mention when not to use or alternatives, but the guidance is helpful for correct usage.

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