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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces 'Read-only' plus adds meaningful context: items carry measured evidence while source records stay in place, and the default status filter is 'open'. It does not cover pagination behavior or what happens with includeDismissed/snoozed semantics beyond the schema wording, so not a full 5.

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?

Front-loads the resource definition and kinds, then defaults/ordering, then routing to siblings — a logical order with no filler. It is fairly dense (several clauses per sentence), which costs a point versus a leaner version, but nothing is wasted.

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?

With 9 optional parameters, no output schema, and no nested objects, the description supplies the conceptual return shape (items with measured evidence, ordered by severity then due time) and points to siblings for detail and mutation. It leaves return-value specifics implicit, but no output schema exists to lean on, so a small gap remains.

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% and each parameter already has a rich description (kind, status defaults, applicationId auth failure mode, category guidance). The description only echoes the default-open behavior and severity ordering, so baseline 3 is appropriate — the schema does the heavy lifting.

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?

States a specific verb+resource ('List Pulse items') and immediately defines the resource as 'the workspace attention queue' with its two kinds, attention and recommendation. An agent can tell this apart from get_pulse_item (single item) without opening either schema.

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?

Explicitly routes: use get_pulse_item for one item's full evidence, update_pulse_item to close one, and read_messages/query_flow_logs for the underlying conversations and logs. It also states the default view (open items, severity then due-time order, matching the dashboard).

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