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

The description opens with 'Create an insider trading alert subscription,' which is a state-changing write, while annotations declare readOnlyHint=true. This is a direct conflict about whether the tool modifies its environment (the calibration treats 'creates' + readOnlyHint=true as a contradiction). The delivery-channel details are useful, but the core behavioral claim contradicts the structured annotation.

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?

Four sentences, front-loaded with the core purpose and reasonably compact. The final clause ('set up insider trade alerts, watch for director buying/selling, or monitor insider activity') is somewhat repetitive, keeping it out of the top score.

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?

An output schema exists, so return values need not be explained, and the description covers purpose, delivery channels, filters, and invocation triggers for a 6-parameter tool. The main gap is that it omits any note of the persistence/idempotency semantics implied by 'Create,' which is exactly where it collides with its annotations.

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 description coverage is 100%, so names, defaults, and examples for all 6 parameters are already documented in the schema. The description restates tickers, minimum value, and trade types without adding syntax or format detail beyond the schema, matching the baseline 3.

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 and resource: 'Create an insider trading alert subscription,' then expands on what is monitored (director share transactions). The 'insider' qualifier implicitly separates it from subscribe_people_alerts, but no sibling is named, so it falls short of explicit differentiation.

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 final sentence gives clear when-to-use triggers: 'set up insider trade alerts, watch for director buying/selling, or monitor insider activity.' It does not cover when-not-to-use or point to alternatives like list_alert_subscriptions for reviewing existing subscriptions.

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