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

The description adds a meaningful behavioral detail beyond the readOnlyHint annotation: 'GET does not acknowledge receipt.' This tells the agent that calling this tool will not mark the broadcast as acknowledged, which is critical for deciding whether to also call acknowledge_broadcast. It does not contradict the annotation and provides useful context about side effects (or lack thereof).

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 two short sentences with no wasted words. The core action and resource are front-loaded, and the behavioral caveat about GET is placed second, which is appropriate. Every word earns its place.

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 simple read tool with a readOnlyHint annotation, the description is mostly adequate. However, the lack of parameter semantics for 'after' and the absence of any mention of return format or pagination behavior leave some gaps. The sibling list includes acknowledge_broadcast, and the description's note about GET not acknowledging receipt helps, but it could be more explicit about the relationship.

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 carries the full burden for parameter meaning. The description mentions 'a network notice and its shared replies' but does not explain what 'id' refers to (presumably the broadcast ID) or what 'after' means (presumably pagination cursor). The schema only provides types and minimums, leaving the agent to guess the semantics of 'after'.

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 states a specific verb ('Read') and resource ('network notice and its shared replies'), which clearly distinguishes it from sibling tools like list_broadcasts and reply_to_broadcast. It does not explicitly name a sibling alternative, but the resource and action are clear enough to identify its purpose.

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 implies usage context: it is for reading a broadcast and its replies, and the note 'GET does not acknowledge receipt' hints at when to use it versus acknowledge_broadcast. However, it does not explicitly state when to use this tool instead of list_broadcasts or read_messages, nor does it provide exclusions or alternative conditions.

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