Merchants Update Merchant

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

Description mentions 'may create or update Monarch data', adding context beyond annotations that indicate it is not read-only and may have side effects (openWorldHint true). Does not specify details like permissions 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?

Short (two sentences) but not maximally concise; the second sentence could be more precise or integrated into the first. Adequate but not efficient.

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?

For a tool with 5 parameters, no output schema, and no parameter descriptions in the description, it is incomplete. Lacks info on what fields can be updated, return format, or error conditions.

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?

Description provides no information about parameters. With only 40% schema coverage, it fails to compensate. Agent receives no guidance on name, fields, output_mode, or session_path.

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 'Update merchant', distinguishing it from siblings like get, delete, list. However, the added sentence about potentially creating data introduces ambiguity.

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?

No guidance on when to use this tool vs. alternatives like merchants_create_merchant or merchants_update_merchant (if it existed). Lacks context for appropriate invocation.

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