list_competitors

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

Annotations cover the safety profile (readOnlyHint=true), so the bar is lower, and the description adds substantial value: it enumerates what each pair contains and explains the app_score vs competitor_score 0-100 comparison. It omits pagination and empty-result behavior, but the payload semantics are well 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?

Two sentences, front-loaded with the core action, then the payload detail, then the sibling pointer. The field enumeration is dense but every element is informative; slightly long, yet without an output schema it earns its length.

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 correctly compensates by describing the returned pair structure and score semantics, and it routes to list_applications for the omitted own-app fields. Missing only meta-behavior like pagination or result limits.

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% and the single app_id parameter is fully documented in the schema as a filter. The description never mentions filtering, so it adds nothing beyond the structured field, which is the expected baseline at high coverage.

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 ('List') and resource ('competitor tracking pairs') and immediately distinguishes the entity from neighboring tools add_competitor/remove_competitor. It also spells out the pair structure, so an agent knows exactly what the resource is.

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?

It gives explicit routing for a related need — 'Use list_applications to get the full metadata of your own app' — clarifying that this tool returns only the trimmed own-app fields. It does not state when-not to use it versus add_competitor/remove_competitor, but the context is clear.

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