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

Goes well beyond annotations by disclosing auth requirements (API key from a specific profile URL) and the precise shape of the failure response (error.code, error.message, http_status, retry_recommended, retry_after_seconds), which is valuable for a mutation tool.

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?

Front-loads the core action, then constraints, auth, and error shape in a compact multi-sentence block. Slightly dense but every sentence carries distinct information.

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?

For a mutation with 10 params, the description covers behavior, constraints, auth, and error handling; an output schema exists so return-value detail is not needed. Missing only edge-case guidance on partial-update semantics.

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 60%; the description compensates by explaining the notify_on_drop/notify_on_rise threshold-free semantics and the 'at least one setting must remain' rule, adding meaning beyond the raw schema.

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?

States a specific verb+resource ('Update a price alert') and enumerates the exact mutation modes (notify_on_drop/rise, thresholds, is_active), clearly distinguishing it from create/delete/get/list siblings.

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 the operational constraint that at least one setting must remain, and names which settings are switchable, but does not explicitly state when to prefer this over create_price_alert or delete_price_alert.

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