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

readOnlyHint=true already declares this a safe read, so the bar is lower. The description adds two genuinely useful facts beyond the annotations: the underlying endpoint (GET /stops/{id}/notes) and that attachments are returned with each note. It says nothing about pagination, ordering, or empty-result behavior.

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?

Two compact sentences with zero filler; the functional purpose is front-loaded and the API endpoint follows as supporting detail. Nothing needs to be trimmed.

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 single-parameter read tool with no output schema and an explicit readOnlyHint, this covers what an agent needs to invoke it correctly, and the attachments note usefully characterizes the payload. Only the sourcing of stop_id and result ordering are left implicit.

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 single stop_id parameter is documented nowhere in structured form. The description partially compensates by embedding '/stops/{id}/notes', which implies stop_id identifies the stop, but it never states the type, format, or where an agent obtains a stop id.

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 and resource ('List all notes on a stop') plus a notable scope detail ('with attachments'). The resource word 'stop' cleanly separates it from sibling locate2u_list_shipment_notes, so an agent can pick the right one 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?

The description gives no when-to-use framing, no prerequisites, and no mention of alternatives such as locate2u_list_shipment_notes or locate2u_add_stop_note. Usage is only inferable from the verb+resource, which is the definition of no real guidance.

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