label_options

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

No annotations provided, so description carries full burden. It explains return fields (id, display name, disambiguating context, contact flags, sole) and data source (same as app form). While it doesn't explicitly state read-only or auth requirements, the nature as a list tool is clear and no contradictions.

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?

Description is a single paragraph that front-loads the main purpose, then details return structure and usage. It is fairly concise given the information needed, with no wasted words.

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 no output schema, description compensates by listing return fields. It explains relationship to sibling tools and env parameter default. Lacks pagination or error handling info, but is reasonably complete for a list tool.

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%, but description adds context: env defaults to dev (safe), shipmentType determines sources (contacts for international, stores for domestic). This adds meaning beyond the enum values.

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 clearly states it lists ship-from/ship-to/importer parties by name, returning IDs and display info. It distinguishes itself from siblings by specifying it should be called before label_preflight/label_create when party IDs are unknown.

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 says when to use: 'Call this before creating a label when you don't already have the party IDs.' It also instructs to show names to user and pass the chosen ID to label_preflight/label_create, and indirectly implies not needed if IDs are already known.

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