Update banner (ad)

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

Annotations already indicate idempotentHint=true and destructiveHint=false. The description adds that structures are sent verbatim, which is useful. No contradictions. But it does not disclose other behaviors like rate limits or auth needs. With annotations carrying part of the burden, the description adds moderate value.

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?

Two concise sentences. The first clearly states the action and affected fields. The second adds essential usage guidance about verbatim structures and the alternative tool for status changes. No wasted words.

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?

With no output schema, the description does not explain return values. While the purpose and parameters are clear, the tool could benefit from stating whether it returns the updated banner or a success message. For a 5-parameter tool with good annotations, it is adequate but not 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?

Schema description coverage is 100%, so baseline is 3. The description reinforces that structures are sent verbatim, aligning with schema descriptions. It does not add new meaning beyond what the schema provides, so score remains at baseline.

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?

Description uses specific verb 'Updates' and resource 'banner', listing fields (name, text blocks, links). It distinguishes from sibling 'banner_action' which changes status, and from 'create_banner'. This clearly identifies the tool's purpose among siblings.

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?

Explicitly directs users to 'banner_action' for status changes, providing an alternative. It gives context on how to use the tool by stating that structures are sent verbatim. However, it does not specify prerequisites or when not to use this tool, missing some guidance.

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