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

No annotations are provided, so the description carries the full burden. It usefully discloses that returned ids map to ParcelShopId for labeling and that the data mirrors GET /api/Parcelshops, but says nothing about result limits, ordering, pagination, or the read-only nature of the call.

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 tight sentences with the core purpose front-loaded and the id-mapping note second. No filler, though the parenthetical API reference is marginal value for an agent.

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 six well-documented parameters and no output schema, the description is adequate but thin: it hints at the id field in the response but does not characterize the returned pickup-point records (address, opening hours, distance) that an agent would need to reason about results.

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 already documents all six parameters including the carrier default (PostNL/DHL/GLS) and organisationId default. The description adds no syntax or format detail beyond what the schema provides, so the baseline of 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?

The description states a specific resource (pickup points / parcel shops) and a scope qualifier ('near an address'), and ties it to the sibling API endpoint GET /api/Parcelshops. It is easy to distinguish from label- and carrier-oriented siblings, though it never explicitly names a competing sibling tool.

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?

There is no when-to-use guidance, no when-not-to-use, and no named alternative among the many sibling tools. The implicit context (finding pickup points near an address) is inferable but the description does not route the agent.

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