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

No annotations provided, so description carries full burden. Discloses that it matches MU-{id} to orders, sets tracking, marks shipped, and is owner-only. Does not cover idempotency, error handling, or potential side effects, but adequately describes the core behavior for a bulk import tool.

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?

Three sentences, no wasted words. Front-loaded with action ('Paste the CSV'), then explains effect and counterpart. Perfectly concise for the information conveyed.

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?

Given the tool's simplicity (2 params, no output schema), description covers all key aspects: source, format, purpose, ownership, and relationship to sibling. Missing details like return behavior or prerequisites (e.g., needing to have used mu_ship_csv first) but adequate for an agent.

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%, baseline 3. Description adds meaning by specifying the CSV source (B2クラウド/e飛伝) and explaining the matching logic. For the courier parameter, enum values are clear. Adds moderate value beyond schema.

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?

Clearly states it imports courier tracking numbers from a specific CSV produced by B2クラウド/e飛伝, explains the content (MU-{id} and 送り状番号), and the effect (matches to orders, sets tracking, marks shipped). Distinguishes from sibling mu_ship_csv as its 'natural counterpart'.

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 states when to use: after issuing labels, paste the CSV. References the counterpart mu_ship_csv, implying sequential usage. Lacks explicit when-not-to-use or alternative scenarios but provides clear context.

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