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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, yet the description still adds return shape (state watched/muted, alertReady, rebaselinePending), the empty-result condition, and a read permission scope. Missing only things like pagination or result ordering, which are unlikely given the fixed per-target list.

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-loaded with the action, then dashboard equivalence and returned fields, then the sibling handoff. Slight redundancy in restating 'permission: read', which annotations already convey, keeps it from a 5.

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?

There is no output schema, so the description carries the burden of describing returned fields, which it does (state, alertReady, rebaselinePending), and it covers the degenerate empty case. Nothing critical for a correct call is absent.

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% and the single `id` parameter is already documented in the schema with its UUID format and origin (GET /targets or POST /targets). The description adds no further detail about the identifier, 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?

States a specific verb ('List') plus the exact resource ('a target's vendors and their monitoring state') and scope ('every detected or watched vendor'). This cleanly separates it from the mutating sibling set_target_vendor_states.

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 state changes to set_target_vendor_states and notes the empty-list case for targets with no journeys. It does not spell out when an agent would prefer get_target or list_targets instead, so a small amount of routing is left implicit.

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