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

There are no annotations, so the description must carry behavioral transparency. It only says 'List', implying a read-only operation, but it does not describe pagination, result ordering, filtering semantics, or what happens when no entries match. This is thin for a tool with no annotation support.

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 appropriately short and front-loads the core purpose before the parameter semantics. Every sentence earns its place, though the opening phrase could be slightly more specific about the catalogue resource.

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 tool with no output schema and no annotations, the description should explain limit behavior, return shape, and likely usage boundaries relative to siblings. It only covers `kind` and `query`, leaving important context for an agent deciding how to call the tool.

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 compensate. It adds meaning by enumerating allowed `kind` values and explaining that `query` filters by name, which is helpful. However, it omits `limit` entirely, leaving that parameter to inference from its name and default.

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 clear action ('List') and a resource ('what PodLexicon covers'), and clarifies the kinds of items included ('podcasts', 'topics', 'guests'). This distinguishes it from the episode-focused siblings, though it does not explicitly name an alternative tool.

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 gives no guidance on when to use browse_catalogue versus the sibling tools. It implies a browsing use case but does not state exclusions or point to alternatives like search_episodes or get_episode.

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