List Delivery Methods

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

The description adds valuable behavioral context beyond the annotations: it explicitly states the read-only nature (consistent with readOnlyHint), and details common failure modes with specific HTTP status codes (401, 403, 404). This helps the agent understand error handling. 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?

The description is moderately sized and includes useful information (API version, endpoint, error codes), but the conflicting statements about a list vs single object are confusing and reduce overall clarity. It is organized but could be more concise and coherent.

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 should clarify the return value structure. It mentions a 'single JSON object' but does not describe the list shape or fields. Pagination behavior is not explained despite the page/per_page parameters. This is insufficient for a list tool with no output schema.

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?

The input schema has 100% description coverage for both parameters (page and per_page), so the baseline is 3. The description does not add any additional parameter semantics, and the contradictory 'single JSON object' statement may confuse pagination behavior.

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 it returns a predefined list of delivery methods, but then says 'Returns a single JSON object describing the delivery method,' which is contradictory. It does not clearly distinguish from sibling tools like list_project_types, and the usage guidance ('when you already know which delivery method you want') is more appropriate for a show tool than a list 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?

The description offers a conditional use case ('Use this when you already know which delivery method you want and need its full field set'), giving some context. However, it does not specify when not to use it or mention alternatives, and the condition itself is somewhat misleading for a list endpoint.

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