Create tracker (write)

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

Annotations already indicate a write operation (readOnlyHint: false) with no destruction (destructiveHint: false). The description adds minimal behavioral info, only noting that it provisions a number, without details on idempotency, rate limits, or side effects.

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?

Very brief (one sentence plus fragment) with front-loaded 'WRITE' label. However, could be more structured; the information is packed but clear.

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 10 parameters, 4 required, nested objects, and no output schema, the description is incomplete. It fails to explain return values, success behavior, or differences between source and session trackers.

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 90%, so baseline is 3. The description adds a hint about using JSON for source-specific config, but does not elaborate beyond what schema already provides for most parameters.

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 'WRITE: Create a tracking number' with specific details about type and provisioning. Distinguishes from sibling tools like delete_tracker or update_tracker as the creation 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?

Mentions using JSON for source-specific config, but lacks explicit guidance on when to use this tool versus alternatives like update_tracker, and does not specify when not to use it.

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