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

Annotations already declare readOnlyHint and openWorldHint=false, so safety is covered. The description adds real value by disclosing the approximate result size ('<=4.8 KB a week'), which lets an agent plan for response volume, but says nothing about pagination, rate limits, or ordering.

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 dense sentences with no filler, and the entry-point marker is front-loaded. The compact notation 'word:p<p>:n' is efficient but opaque enough to cost a little clarity.

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?

There is no output schema, but the description compensates partially by enumerating returned fields, which is genuinely helpful. Against six entirely undocumented parameters and no guidance on the JSON/TSV/markdown formats, the definition is only partially complete for a tool of this complexity.

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 0% across six parameters, so the description carries the full burden and mostly fails. Only the 'days' window is loosely conveyed via 'next N days'; the roles of 'all', 'fields', 'format', 'markets', and 'category' are never explained.

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 concrete resource and scope ('earnings calls with mention markets in the next N days') and previews the returned fields (entity, venues, word count, top3). It is clear what the tool returns, though it never names a sibling alternative to distinguish itself from 'list_calls' or 'screen'.

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?

'START HERE' is a genuine workflow directive that implies this is the entry point of a session. However, there is no explicit when-not guidance, no prerequisites, and no named alternative for narrower queries.

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