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

Annotations already provide idempotentHint=true and destructiveHint=true, and the description adds valuable specifics: it is a soft-disable scoped to the caller's account, returns {removed: false} when already inactive, and raises unknown_ticker for unrecognized symbols. This goes well beyond the structured annotations.

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?

The description is compact and front-loaded with the operation type and effect. There is slight redundancy between 'deactivates a saved subscription' and 'soft-disable the caller's news-alert subscription,' but every sentence otherwise contributes behavioral or error 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 one-parameter tool with an output schema, the description is complete: it covers the operation, account scoping, idempotency behavior, a concrete return case, and the main error condition. Nothing essential is missing for correct invocation.

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% and the ticker parameter is already documented. The description adds extra meaning by clarifying that an unrecognized symbol will raise unknown_ticker, so the agent knows the value must correspond to a recognized ticker, not merely match the pattern.

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 a specific verb and resource: it deactivates/soft-disables the caller's news-alert subscription for a given ticker. This distinguishes it from siblings like alphai_alerts_subscribe and alphai_alerts_list, even without naming them.

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?

The description makes the use case clear: the caller wants to deactivate an existing ticker alert subscription. It does not explicitly list alternatives or exclusion conditions, but the operation type and idempotent behavior give sufficient context for selection.

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