get_negative_keyword_list_keywords

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

Annotations already declare readOnlyHint=true, so the description adds no additional behavioral context beyond stating it lists keywords. It does not disclose any side effects, authentication needs, or rate limits, which are already covered by annotations.

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 concise sentences: first states purpose, second explains the key parameter. No unnecessary words, well-structured and front-loaded.

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?

Given the presence of an output schema and annotations covering read-only behavior, the description provides essential context. However, it omits details on pagination, filtering, or order of results, which would be helpful for a list tool but are not critical.

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?

With 0% schema description coverage, the description partially compensates by explaining shared_set_id as 'numeric ID from get_negative_keyword_lists (shared_set.id).' However, customer_id is left unexplained, 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 'List the keywords inside a shared negative keyword list,' which is a specific verb and resource. It distinguishes from sibling tools like 'get_negative_keyword_lists' (which lists lists) and 'add_to_negative_keyword_list' (which adds keywords).

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 implies a prerequisite (shared_set_id from get_negative_keyword_lists) but does not explicitly state when to use this tool versus alternatives or provide exclusions. For a simple retrieval tool, this is minimally adequate but lacks clear guidance.

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