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

Beyond the readOnlyHint annotation, it discloses the projection method ('from its own filing cadence') and unusual behaviors ('held, not rolled, marked overdue when lapsed'). This is exactly the kind of non-obvious behavioral context that helps an agent set expectations.

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 key purpose and usage are front-loaded, with exclusions and a brief arg list. Dense but efficient; the only minor waste is the arg name list that duplicates schema property names.

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 read-only tool with an output schema, the behavioral and routing context is solid. However, with no parameter descriptions in the schema, the ambiguity around types and limit leaves an agent guessing about valid invocations.

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 the description should clarify entity, types, and limit. It only lists the argument names and implies entity is a company via context; it does not define what values types accepts, what limit controls, or how they interact. The natural language hints at trial readouts vs earnings but does not map them to types.

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 names a specific resource (upcoming company dated events) and a specific action (returns nearest-first earnings projections and trial readouts). It also explicitly distinguishes itself from get_filings and answer, so an agent can tell what it is not.

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?

It explicitly says when to use the tool ('when does X report next; what's coming up for X') and gives exclusions ('Not for past events → get_filings; what the earnings were → answer'). No inference is required.

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