add_tracked_keywords

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

It discloses that the operation appends to existing lists with no duplicates, and that inputs can be lists or comma-separated strings. Since annotations only include a title, the description carries the burden and adds meaningful behavioral context, though it lacks details on error handling or reversibility.

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 concise and well-structured: a one-sentence summary, a usage note, and a parameter list. Every sentence adds value, and the format is easy to scan.

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?

It covers purpose, prerequisites, parameter semantics, and constraints. The omission of the 'config' parameter and lack of return value details are minor gaps, but overall it is sufficiently complete for a simple append operation without an output schema.

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?

The schema has 0% description coverage, so the Args section in the description is essential. It explains project_id, keywords, competitors, and locations with types and semantics. However, the 'config' parameter in the schema is not mentioned, leaving a gap.

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 clearly states it adds tracked keywords, competitors, and/or target locations to a project. The verb 'Add' and resource are specific, and it distinguishes itself from the sibling tool add_tracked_prompts by naming the exact entities.

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 provides a clear prerequisite (call list_projects() first to get the project_id) and a constraint (at least one of keywords/competitors/locations must be provided). However, it does not explicitly mention alternatives or when not to use this tool, 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.