List Broadcasts

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

The readOnlyHint annotation already indicates a safe read operation. The description adds context about optional filtering and pagination, but does not detail pagination behavior (e.g., default limit, max page) or sorting. No contradictions with annotations.

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 a single sentence that front-loads the main action and includes optional details efficiently. Every part adds value without extraneous text.

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 is simple with optional filters and pagination, and no required parameters. However, no output schema is provided, and the description does not explain return values or pagination mechanics (e.g., total count, cursor). Slightly below complete for a list endpoint.

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% with clear parameter descriptions. The description restates that status is a filter and page/limit are for pagination, adding no new meaning beyond what the schema provides. Baseline 3 is appropriate.

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 tool lists all broadcasts with optional filtering by status and pagination. It uses a specific verb ('List') and resource ('broadcasts'), and the context of siblings like 'neuron_get_broadcast' distinguishes it as a list operation.

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?

It implies when to use (listing broadcasts) and hints at optional filters and pagination, but does not explicitly state alternatives or when not to use. The sibling list includes 'neuron_get_broadcast' which could be the alternative for single retrieval, but no direct guidance is given.

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