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

Annotations already establish this is a non-read-only, non-idempotent, non-destructive write. The description adds real behavioral context beyond that: it runs synchronously ('runs at once') and enumerates the two refusal conditions, which an agent needs to anticipate failure modes.

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 tight sentences with no filler; the core action and downstream benefit are front-loaded, followed by the constraints. Efficient, though slightly dense in the first clause.

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 write tool with no output schema, the description covers the effect, the synchronous behavior, and the failure conditions, and routes the agent to a context-reading sibling. It is complete enough to call correctly, missing only return-value expectations.

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 100%, so the schema already documents name, aliases, domains, and project_id. The description only alludes to name uniqueness via the refusal condition and adds no syntax or format detail beyond the schema, so 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?

Uses a specific verb (track/add) and resource (competitor) and explains the downstream effect: visibility reads rank the competitor's mentions and citations beside your brand. This clearly distinguishes it from the sibling remove_competitor.

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?

States concrete refusal conditions (name already tracked, competitor limit reached) and points to get_project_business_context to see who is tracked now. It gives clear context for when the call will succeed but does not explicitly name remove_competitor or other alternatives.

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