List competitors

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), and the description adds real value by disclosing that results nest monitors under each competitor with last_run, which no output schema provides. It stops short of noting ordering, pagination, or behavior for workspaces with no competitors.

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?

Front-loaded with the action and return shape, and the routing guidance follows immediately. Slight overlap between the enumerated fields in sentence one and the 'overview of what is tracked' framing in sentence two, but nothing is wasted or buried.

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?

For a single-parameter read tool with no output schema, the description covers what is returned at a useful level of detail and how it differs from the sibling. Minor gaps: no indication of ordering, volume, or whether discovery_status values have meaning an agent should act on.

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?

Only one parameter (workspace_id) and schema description coverage is 100%, with the schema already pointing to list_workspaces/create_workspace as its source. The description adds no additional semantics about the parameter, 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 the competitors in a workspace') and even sketches the return shape (discovery_status, nested monitors with last_run). It explicitly distinguishes itself from the closest sibling, list_monitors, so an agent can choose without opening a schema.

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?

Gives a positive condition ('Use it for an overview of what is tracked') and names the alternative plus its selecting condition ('to list monitors alone or filter them by competitor, use list_monitors'). This is the when/when-not/alternative pattern done correctly.

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