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

With no annotations provided, the description carries full responsibility for transparency. It states this is a 'PURE READ of already-stored data (no live fetch, no X cost)' and includes a security warning about untrusted third-party content. This informs the agent about side effects and safety beyond what annotations would have covered. It does not detail pagination or error behavior, but for a read-only retrieval the core transparency is adequate.

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 front-loaded with an engaging question and a clear output list, then efficiently contrasts with alternatives, gives a prerequisite, and adds a security note. Each sentence serves a distinct purpose. It is longer than a minimal description, but the structure keeps it readable and well-organized without fluff.

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 the tool's moderate complexity and the presence of an output schema, the description covers the essential aspects: what it returns, how to prepare the input, and a security caveat. The only notable gap is the undocumented 'limit' parameter, but that is a minor omission given the tool's straightforward nature. Overall, an agent can use this tool correctly with the provided guidance.

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%, so the description must explain both parameters. It clarifies that 'handle' must be a resolved @handle (via resolve_analyst), which adds meaning. However, it never explains 'limit' (its effect, range, or default). Since limit has a default of 15, the omission is less critical, but the description still fails to fully compensate for the schema's lack of explanation.

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 opens with a concrete question and then enumerates the exact output fields (ticker, direction, date, link, snippet). It explicitly distinguishes itself from analyst_track_record (accuracy) and a live timeline pull, making the tool's purpose unmistakable. The specific verb phrase 'most-recent STORED calls' leaves no ambiguity about what the tool returns.

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 provides a clear alternative (analyst_track_record) and a prerequisite (resolve_analyst first). It also contrasts with a live timeline pull. It does not exhaustively cover all siblings (e.g., analyst_views), but the key decision-relevant context is given, so an agent can choose this tool appropriately.

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