List competitors

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows this is a safe read operation. The description adds the scope (per project) and content (competitors, market data, suggestions). However, it doesn't disclose pagination behavior (cursor/limit semantics), whether all results are returned by default, or the shape/format of the returned data, which would be useful for a list tool with no output schema to clarify.

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 a single concise sentence that packs the core purpose efficiently. It's front-loaded with the primary action and scope. It could arguably be split or expanded with usage guidance, but as written it is economical with no wasted words.

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?

This is a paginated list tool (limit, cursor) with no output schema, yet the description provides no information about pagination semantics, default result count, ordering, or what 'market data and suggestions' concretely means. For a list tool with two undocumented parameters and no output schema, the description is thinner than it should be to reliably guide an agent.

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 description coverage is only 33%, so the description should help clarify the undocumented parameters (limit, cursor). The description does not explain limit or cursor semantics at all, relying entirely on the schema's type/min/max constraints (which offer no semantic meaning). The project_id parameter is well documented in the schema itself. Given the moderate coverage gap and lack of param explanation, the description adds minimal value beyond the schema.

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 'List tracked competitors, market data, and suggestions for a project' clearly states the verb+resource (list competitors) and scopes to a project. However, it doesn't distinguish from the closely related sibling tools add_competitor/remove_competitor, though the list-vs-mutate distinction is somewhat implicit. The mention of 'market data and suggestions' adds some scope clarity.

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 does not state when to use this tool vs alternatives. It doesn't note that competitors are per-project, doesn't mention pagination behavior with the cursor/limit params, and offers no exclusions. There are related tools like analyze_backlinks and list_ranked_keyword_suggestions that could overlap conceptually with 'market data and suggestions,' but no differentiation is provided.

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