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

Annotations already declare readOnlyHint=true, and the description reinforces this with 'Read-only.' It adds useful behavioral context beyond the annotation: defaulting to open items, ordering by severity then due time in dashboard order, carrying measured evidence, and clarifying that counted conversations/log rows are not moved or deleted.

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 dense but every sentence earns its place: purpose, item kinds, read-only nature, default ordering, evidence semantics, and sibling routing. It is front-loaded with the core purpose and does not waste words.

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 read-only list tool with nine parameters and no output schema, this description covers the essential context: what items are, how they are ordered, what they contain, how to access related data, and when to use sibling tools. Nothing critical is missing for an agent to invoke it correctly.

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 coverage is 100%, so the baseline is 3. The description adds extra meaning beyond the schema by giving concrete examples of attention items ('failing flows, a failed broadcast, an unsubscribe spike') and clarifying the queue's ordering semantics. This enriches parameter understanding even though most parameter-level detail already lives in the schema.

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 opens with a specific verb and resource: 'List Pulse items — the workspace attention queue.' It clearly distinguishes the two item kinds and explicitly points to get_pulse_item and update_pulse_item as alternatives, so an agent can tell exactly what this tool does and how it differs from siblings.

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 explicitly says when to use alternatives: 'Use get_pulse_item for one item's full evidence and proposed change, and update_pulse_item to close one.' It also explains that referenced conversations and log rows stay in place and are reachable with read_messages and query_flow_logs, giving clear routing guidance.

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