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

The description adds meaningful behavioral context beyond the annotations: it specifies 'Execution: synchronous,' 'Task support: forbidden,' and notes that the returned JSON is internal application state for orchestration, advising against displaying raw JSON. These details are not present in the readOnlyHint, idempotentHint, or destructiveHint annotations. No contradiction with annotations exists.

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 moderately concise, but it front-loads the tautological 'list competitors' and then devotes most of its length to response-handling directives. The classification and execution details are useful, but the structure could be improved by leading with a substantive purpose statement and moving the orchestration notes to the end.

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 9 undocumented parameters, no definition of 'competitors,' and no distinction from sibling competitor-intelligence tools, the description fails to provide sufficient context for an agent to decide when or how to call this tool. The presence of an output schema helps interpret returns, but the opaqueness of the inputs and the tool's place in the broader workflow remain significant gaps.

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 lists 9 parameters with 0% description coverage, and the tool description provides absolutely no explanation of limit, cursor, seatId, status, seatName, accountId, campaignId, creativeId, or advertiserId. The description does nothing to compensate for the complete lack of parameter documentation.

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 opens with 'list competitors' which merely restates the tool name without explaining what competitors are or how they relate to other competitor-related tools. It provides no differentiation from siblings like get_competitor_intelligence or leanriq_get_competitor_creative_intelligence, leaving the agent unable to determine the tool's specific scope and 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?

No guidance is given on when to use this tool versus alternatives. The only operational instruction ('Use assistantSummary first when responding to the user') concerns response formatting, not tool selection. The description lacks any mention of appropriate contexts, prerequisites, or exclusions.

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