get_packing_slip_templates

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

No annotations are provided, so the description carries full weight. It simply says 'Fetch', implying read-only but not stating it. No disclosure about return format, pagination behavior, rate limits, or whether it lists all templates or requires filters.

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?

One short, focused sentence with no filler. It is appropriately sized for a simple fetch operation, though slightly under-specified.

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?

The tool is simple, but the description omits return value expectations and pagination behavior. No output schema exists, and the description doesn't mention that it returns a list of templates or how pagination works. Minimal information for an agent to fully understand invocation 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 descriptions cover 100% of parameters (after, first). The description adds no parameter context, but the schema already documents cursor and count semantics. Baseline 3 is appropriate when schema handles the details.

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 uses a specific verb ('Fetch') and resource ('packing slip templates'), clearly distinguishing it from sibling create/update/delete operations. It doesn't differentiate from other 'get' tools, but the resource is specific enough.

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?

No guidance on when to use this tool versus alternatives. It doesn't mention pagination strategy, ordering, or any prerequisites. The context implies read operation, but no explicit when/when-not guidance.

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