sc_price_alert_add

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

With no annotations, the description carries the full burden. It mentions the write permission requirement, but does not describe side effects, error handling, or what happens if both or neither isin/ticker are provided. Partial transparency.

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 concise sentences with no filler. Directly states purpose, usage condition, and permission requirement. Excellent structure.

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?

Tool is simple, and output schema exists, so return values need not be explained. However, the description omits the portfolio_id parameter and does not clarify error scenarios or mutual exclusivity of isin/ticker, making it incomplete for full usage.

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 0%, so description must compensate. It explains isin and ticker partially (must provide one), but does not explain price (units, meaning) or portfolio_id. Compensation is insufficient.

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 action ('Add a price alert') and resource ('price alert'), distinguishing it from sibling tools like sc_price_alert_remove. The description is unambiguous.

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 a condition for usage ('Provide either isin or ticker') and a prerequisite (SC_MCP_ENABLE_WRITES=true). However, it does not explicitly mention alternatives or when to use this tool over others, though the name and purpose make it implicit.

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