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

Annotations only declare a non-readOnly, non-destructive, non-idempotent write; the description goes well beyond by disclosing the conflict outcome, the implicit side effect of approving/reviving a queued suggestion while preserving its mention history, and the fixed own-brand constraint. This is exactly the kind of hidden-behavior disclosure annotations cannot carry.

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?

Three sentences, no filler, and the core action is front-loaded before the two edge-case behaviors. Each sentence carries distinct decision-relevant information.

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 an 8-parameter creation tool with no output schema, the description covers the critical behavioral quirks and error mode. It omits what the call returns and any permission/rate-limit expectations, but the structured fields plus annotations mean little else is needed to invoke it correctly.

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 every parameter (color, status, domains, useRegex, nameRegex, trackedNames, workspaceId) is already documented in the schema. The description adds no parameter-level syntax or defaults beyond the implicit note that new brands are competitors, which does not map to a specific field, so the baseline 3 applies.

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?

States a specific verb and resource ('Add a competitor brand to track in AI answers') and immediately scopes it against siblings: it is not update_brand, and the CONFLICT clause clarifies it is a create-only path. An agent can distinguish it from approve_suggested_brands and delete_brand without opening any schema.

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?

Gives clear conditional routing: if the name already sits in the suggestion queue it approves/revives that suggestion, and if an existing tracked brand shares the name it fails with CONFLICT. It does not explicitly tell the agent when to prefer approve_suggested_brands or update_brand, so it is strong context without full alternative/exclusion guidance.

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