Add Price Alert

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

Annotations indicate a write operation (readOnlyHint=false) and not destructive (destructiveHint=false). The description adds that it returns the created alert object, but lacks details on side effects like whether duplicate alerts are allowed or if there are rate limits.

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?

Three short sentences, each carrying essential information. No fluff or repetition. The structure is clear: purpose, then parameter options, then return value.

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?

While the description covers basic usage, it lacks information about required parameter formats (e.g., price string format), potential errors, or prerequisites (e.g., symbol must exist). For a 4-parameter tool with no output schema, more context would be beneficial.

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%, but the description adds value by explaining possible values for 'condition' and 'frequency' with examples (e.g., 'once (trigger once then disable)'). This goes beyond the schema's property descriptions.

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 a price alert, with specific verb 'Add' and resource 'price alert'. The description lists condition and frequency options, distinguishing it from sibling tools like alert_delete, alert_list, etc.

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?

Describes the condition and frequency options, which helps the agent know how to configure the alert. However, it does not explicitly state when to use this tool versus alternatives or when not to use it (e.g., if alerts already exist for the symbol).

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