list_competitors

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

The readOnlyHint annotation already establishes this is a safe read operation, and the description adds concrete behavioral expectations by enumerating the returned metadata and the 0-100 app_score vs competitor_score comparison. It does not contradict the annotation and provides more transparency than the bare annotation alone.

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 compact but information-dense, front-loaded with the core action and then unpacking the return value in a structured way. No filler or redundant restatement of the tool name appears.

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?

Even without an output schema, the description fully tells an agent what to expect: each pair includes metadata for both apps and both key visibility scores. It also clarifies the semantic purpose (direct ASO comparison), making the tool self-explanatory for selection and invocation.

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 input schema has full parameter description coverage with 'Filter competitors by application internal ID', so the description does not need to add much. It does not elaborate further on the filtering behavior or how the optional app_id affects the list, but the schema already conveys the meaning.

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 a specific verb+resource construct: 'List competitor tracking pairs.' It clearly distinguishes the tool from siblings like add_competitor and remove_competitor by focusing on listing existing pairs, and it further clarifies the output includes app metadata and visibility scores for ASO comparison.

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?

The description gives clear context for when to use this tool: to see tracked competitor pairs and directly compare visibility scores. It does not explicitly state exclusions or alternatives, but the sibling names make the contrast visible and the phrase 'for direct ASO comparison' signals the intended use case.

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