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

Annotations are minimal (non-read-only, non-destructive). The description adds value by disclosing that FREE businesses are blocked, and that access must be verified before use. This exceeds annotation content, though it does not mention possible side effects like order status updates.

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 4 sentences and front-loads the purpose. It is efficient but could be slightly more concise by trimming 'Before offering this action or requesting its inputs' to 'Before using this tool'.

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 description covers purpose, usage guidelines, and permission checks, but omits parameter meanings and output/return value. Given the tool has 6 parameters and no output schema, this leaves notable gaps for an agent to use the tool correctly.

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 0%. The description only explains the 'confirm' parameter (requires 'SHIP'), leaving 5 other parameters (notes, orderId, communityId, trackingNumber, shippingProvider) unexplained. This provides minimal help to the agent.

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 the purpose: 'Mark a physical product order as shipped.' This is a specific verb+resource+action, and it uniquely identifies the tool among siblings, as no other tool performs this exact action.

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 provides explicit guidance: check business permissions, note that FREE businesses cannot use it, call check_business_tool_access before inputs, and show warnings before proceeding. It also specifies that confirm must be set to SHIP, giving clear when-to-use and prerequisite instructions.

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