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

Annotations already declare readOnlyHint=true, and the description reinforces that while adding meaningful context: the item includes underlying evidence and ids, and automatic resolutionPolicy items close themselves and cannot be closed by hand. No contradiction 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?

Three short sentences front-load the main purpose, then add the prerequisite and a domain caveat. Every sentence contributes distinct information, and there is no filler.

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 two-parameter read tool with no output schema, the description explains what the response contains, notes the list_pulse_items prerequisite, and flags the resolutionPolicy behavior that could affect downstream decisions. Nothing essential is missing.

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%, so the schema fully documents itemId and applicationId, including the MCP_APPLICATION_REQUIRED failure mode. The description only restates the itemId source ('as returned by list_pulse_items') without adding parameter detail beyond the schema, so baseline 3 applies.

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?

Description opens with a specific verb-resource pair ('Return one Pulse item in full') and enumerates the content: measured evidence, conversation and execution-log ids, and the change Apply would build. This clearly distinguishes it from list_pulse_items and update_pulse_item.

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 explicitly states the prerequisite 'Call list_pulse_items first to get the itemId' and labels the operation as read-only. It does not name an alternative tool or state when not to use it, but the 'one item in full' framing and read-only marker provide clear usage context.

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