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

Annotations already provide readOnlyHint=true, and the description confirms "Read-only". The description adds that the tool returns "speaker-tagged" chunks and supports optional filtering, which goes beyond the annotation. No contradictions or missing critical behavioral traits (e.g., no pagination detail, but acceptable given the simplicity).

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: the first succinctly describes the action and options, the second explains the use case. Every word earns its place; no redundancy or filler.

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?

The tool has 6 parameters (all documented in schema) and no output schema. The description explains the purpose and use case adequately. It could mention that results are ordered by speaker or time, but omitting that is a minor gap given the simplicity. The description is complete enough for an agent to understand what to expect.

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%, so baseline is 3. The description adds meaning by explaining the purpose of filtered chunks (qualitative judgment) and emphasizing the "exact Bullrun ticker" requirement. It also frames the optional filters (fiscal period, search text) in the context of finding specific transcript content, which helps an agent select parameters meaningfully.

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 verb "Fetch", the resource "speaker-tagged earnings-call transcript chunks", and the specific scope "for one exact Bullrun ticker". It distinguishes the tool from its siblings (which are portfolio, position, and financial metrics tools) by focusing on qualitative transcript data.

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 explicitly tells the agent to use this for "management guidance language, analyst Q&A, and qualitative judgment that is not visible in financial statements". This provides clear context for when to invoke this tool over siblings like get_financial_history or get_forward_estimates. It does not explicitly state when not to use it, but the positive guidance is sufficient.

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