Subscribe to ticker alerts

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

Annotations indicate idempotentHint=true (non-destructive, read-write). The description adds behavioral details: partial update preserves omitted fields, new subscription defaults min_relevance_score to 6, and error conditions. This goes beyond 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?

Two sentences contain all essential information: action, optional params, behavior (partial updates, defaults), and errors. No fluff, front-loaded with the main purpose.

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 annotations and output schema, the description covers input behavior, defaults, and errors. It could mention that the output is a subscription object, but output schema likely handles that. Adequately complete for a subscription tool.

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% with descriptions. The description adds value by clarifying usage (e.g., 'category_filter restricts which categories trigger', 'min_relevance_score raises the threshold') and explaining defaults and partial update semantics.

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 the action ('subscribe the caller to ticker news alerts') and resource, differentiating from siblings like unsubscribe and list. It specifies optional filters, making the purpose precise.

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 explains optional parameters, partial update behavior, defaults, and possible errors (tier_not_paid, unknown_ticker, limit_reached), providing good guidance. However, it does not explicitly contrast with alternative tools like alphai_alerts_unsubscribe.

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