direct_add_sitelinks

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

No annotations are present, so the description carries the burden. It discloses the write nature, length constraints (Title≤30, Desc≤60), and the need for allow_write=true to mutate live cabinet. It adds context beyond the schema, though it doesn't discuss error cases or side effects like overwriting.

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 concise and front-loaded. The description starts with 'WRITE:' to immediately signal mutation, then packs essential details (structure, constraints, return value, flag) in two short sentences with zero fluff.

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 mutation tool with 3 parameters and no output schema, the description covers the main parameter, constraints, and return value. It doesn't explain dry_run's behavior, which is a notable gap, but overall it's sufficient for an agent to understand the tool's core function.

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 only 33%, but the description explains the sitelinks array structure with title, href, optional description, and length limits. It mentions allow_write but does not clarify dry_run; however, the schema provides a description for allow_write, partially compensating. The missing dry_run explanation is a minor gap.

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 ('sitelinks.add set') and the resource being manipulated, with a 'WRITE:' prefix indicating mutation. It distinguishes itself from sibling tools like direct_list_sitelinks by specifying an add operation, and includes return value (SitelinkSetId).

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?

Provides clear context as a write operation and mentions the allow_write=true requirement for live actions. It doesn't explicitly name alternatives or exclusions, but the intent is unambiguous given the sibling list of tools.

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