list_competitors

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: the user's own domain is included and flagged isOwn:true, rows carry id/domain/isOwn/preparationStatus/createdAt, and there is a non-obvious gotcha that no display name exists on this list. That last point is exactly the kind of trap an agent would otherwise fall into.

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?

Three front-loaded sentences: purpose, then payload contents, then the display-name caveat. No filler. The third sentence is slightly tangential to invocation but earns its place as a data-interpretation warning.

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?

There is no output schema, so the description carries the burden of explaining the return shape and does so by enumerating every field and explaining preparationStatus. Combined with the annotations, an agent has enough to call and interpret the tool, though pagination or list-size behavior is unaddressed.

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 projectId parameter is fully documented in the schema, including its source ('from list_projects') and pattern. The description adds no further parameter detail, so the baseline 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?

States a specific verb and resource ('List all competitors being monitored for a project') and scopes it to a project, which cleanly separates it from the singular sibling get_competitor. An agent can tell immediately that this is the enumeration tool rather than the single-item fetch.

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?

Usage is implied by 'being monitored for a project' and the requirement for a projectId, so an agent can infer it is the entry point for competitor enumeration. However, it never states when to prefer it over get_competitor or what to do when the list is empty, and it names no alternatives explicitly.

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