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

No annotations are provided, so the description carries the full burden. It adds context by clarifying that transmissions include blog posts and pings, but does not disclose return format, ordering, pagination, or any side effects. Since it's a list operation, it is implicitly read-only, but that is not stated. The behavioral transparency is minimal.

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 concise sentence that front-loads the purpose. It contains no filler and every word adds meaning. It is appropriately sized for a simple list tool.

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 no-parameter list tool without an output schema, the description is mostly adequate: it states the resource and clarifies the content. However, it omits details like whether the list is paginated, sorted, or what fields are returned. Given the absence of an output schema, more explicit return-value information would be helpful, but it is not critical for a basic list.

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?

The tool has zero parameters, so the description does not need to elaborate on parameter meaning. The schema already shows an empty object, and the baseline for 0 parameters is 4. The description adds no parameter-specific information, which is acceptable given there are none.

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's purpose: to list all transmissions, explicitly scoped to 'blog posts and pings'. It uses the specific verb 'list' and resource 'transmissions', distinguishing it from 'read_transmission' (which implies reading a single transmission). The scope is unambiguous.

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?

There is no guidance on when to use this tool versus alternatives like 'read_transmission' or 'list_agents'. The description does not mention any conditions, exclusions, or alternative tools. An agent would have to infer that 'list' is for all and 'read' is for a specific one, but no explicit routing is provided.

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