Register Package for Tracking

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

Annotations indicate a write operation (readOnlyHint=false), which aligns with the description's 'Register' action. The description adds value by disclosing quota consumption and that it returns detected carrier and registration status. No contradictions 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 three sentences, uses an emoji for emphasis, front-loads the action, and contains no unnecessary information. Every sentence earns its place.

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 order, quota, return value, and carrier auto-detection. With annotations and output schema present, it provides sufficient context. Minor missing detail on duplicate registration handling, but overall complete.

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 already has detailed descriptions for both parameters (tracking_number and tag), with 100% coverage. The description reinforces the auto-detection behavior for tracking_number but doesn't add new meaning. Baseline 3 is appropriate.

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 action (register a tracking number), purpose (begin monitoring shipment status), and key features (auto-detects carrier from 3,200+ carriers, must be called before tracking.status). It effectively distinguishes the tool from siblings like logistics.tracking.status.

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 explicitly states 'Must be called before tracking.status', providing clear guidance on when to use the tool. It also mentions quota consumption (200 free/month). While it doesn't explicitly state when not to use it, the context of siblings and the prerequisite nature makes it clear.

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