Создать набор быстрых ссылок

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

Beyond the annotations (readOnlyHint=false, idempotentHint=false), the description discloses the immutability behavior and the need to reassign the set, which are important side effects not captured elsewhere. This adds meaningful transparency for the agent.

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 two sentences, front-loads the action, and states the key constraint (immutability) and follow-up action (reassign) efficiently. There is no extraneous information, and the structure is clear and easy to parse.

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 the absence of an output schema and the presence of sibling tools, the description covers the essential behavioral aspects: what it does, the item limit, and the immutability implication. It could explicitly state that the created set is not automatically assigned to an ad, but the phrase 'reassign' implies this, so it is sufficiently 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 schema already describes the 'sitelinks' parameter with the same range (1-8 items) and item details. The description does not add new parameter-level information beyond reiterating the range, so it meets but does not exceed the baseline for full schema coverage.

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 ('Creates a set of quick links') and specifies the resource and its constraints (1-8 items). This distinguishes it from sibling tools like get_sitelinks and delete_sitelinks, leaving no ambiguity about the tool's purpose.

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 explains that sets are immutable and that to change links, one must create a new set and reassign it to an ad. This provides clear guidance on when to use this tool (for initial creation or replacement), covering the primary use case without explicitly listing alternatives.

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