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

Annotations already cover readOnly/idempotent/destructive, but the description adds real behavioral context: the 12-item cap, ranking order, the evidence categories behind each suggestion, and the precise semantics of swap_out (the mined competitor with fewest receipt sites). It does not mention pagination or auth, but the cap and swap semantics are non-obvious and usefully disclosed.

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?

It is a single front-loaded sentence that starts with the resource, which is good. However it is a run-on packed with six enumerated 'why' examples and parenthetical detail that is heavier than needed for tool selection.

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 carries the return-value burden and does so well, explaining the suggested brands, their rationale fields, and swap_out. It is largely complete for a read-only, single-param tool, missing only explicit routing to the add/dismiss sibling tools.

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?

Only one parameter (app_id) exists and the schema already documents it at 100% coverage, including the 'omit to use most recent project' behavior. The description adds nothing about the parameter, so the baseline of 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?

The description concretely states what the tool returns: up to 12 mined brands not on the competitors list, ranked best-first, with the 'why' signals and a swap_out target. This distinguishes it from list_competitors and get_partners, though it never names those siblings explicitly.

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?

There is no explicit statement of when to call this versus list_competitors, add_suggested_competitor, or dismiss_competitor_suggestion. The 'at the cap' swap_out detail implies a scenario, but the agent must infer the workflow and follow-up actions.

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