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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile needs no restating. The description adds real value by disclosing the shape of the response (aggregated appearances, first/last show, top topics, recent segments) in the absence of an output schema. It says nothing about behavior when the speaker is unknown, handle-format handling, or result size/cost.

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?

One sentence, front-loaded with the subject and then a colon-delimited list of what the caller gets. No preamble, no redundant restatement of the title.

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 one-parameter, read-only lookup with no output schema, the description supplies the essential return-content detail an agent needs to decide whether to call it. Missing only edge-case behavior (unknown speaker, ambiguous matches), which keeps it from a 5.

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% and the single parameter already documents the name-or-handle form with concrete examples. The description's 'by name or X handle' echoes that, which is mild reinforcement rather than added meaning. Baseline 3 applies when the schema carries the semantics.

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 the resource (an ATC speaker, identified by name or X handle) and enumerates what the profile contains: appearances, first and last show, top topics, recent segments. That is specific enough to distinguish an aggregated profile from a plain listing. It stops short of naming the closest sibling, speaker_calls, which plausibly returns a call list rather than a profile, so an agent must infer the split.

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?

Usage is implied by the content list: reach for this when you want an overview of a speaker rather than a transcript search. There is no explicit when-to-use statement, no exclusions, and no mention of speaker_calls or search_segments as alternatives for narrower questions.

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