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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the trailing 'Read-only.' merely repeats structured data. The one genuine addition is 'including available limit metadata', which tells the agent the response carries quota/limit context. No mention of pagination, behavior when no competitors are tracked, or ordering.

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?

A single sentence with the resource and scope front-loaded, followed by one short pointer about limit metadata. Nothing is redundant except the redundant 'Read-only.' tail, which is minor.

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 an output schema present and annotations covering the safety profile, the description only needs to convey scope and selection intent, which it does for a simple two-parameter list tool. The gap is the undocumented projectId and the lack of guidance on default-store behavior at the description level.

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 50%: storeProvider is documented with its default fallback, while projectId has only a uuid pattern and no prose. The description's 'for a project and store' mirrors the two parameters but adds no format, requiredness, or fallback detail beyond the schema, so the baseline 3 holds.

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 ('Lists the competitor apps currently tracked') plus the scoping dimensions (project, store) and an extra output detail (limit metadata). This is unambiguous, though it doesn't explicitly name the sibling it differs from (e.g., suggest_keyword_competitors or add_keyword_competitors).

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?

'Currently tracked' implicitly signals this reads existing competitors rather than suggesting or adding them, which is enough to distinguish from suggest_keyword_competitors. However, there is no explicit when-to-use statement, no mention of prerequisites such as a project having competitors configured, and no alternative named.

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