get_keyword_search

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

No annotations are provided, so the description must carry the full burden. It only mentions what the tool returns but does not disclose behavioral traits such as whether it is idempotent, what happens if the search is still running, authentication needs, or rate limits. The description is minimal for transparency.

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 extremely concise: two sentences with no wasted words. It is front-loaded with the action and key information. Every sentence serves a purpose.

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?

The tool is simple with one required parameter. However, the description lacks detail about the returned structure: it mentions 'search status, analytics summary, and posts' but does not elaborate on what those contain. Without an output schema, the description could be more complete in explaining the response format.

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%, with the parameter 'id' described as 'Keyword search ID' in the schema. The description does not add any additional meaning beyond the schema. Baseline is 3 due to high coverage, and no extra value is provided.

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 the verb ('Get'), the resource ('results for a keyword search by ID'), and the outputs ('search status, analytics summary, and posts'). It distinguishes from siblings like 'keyword_search' (which likely initiates a search) and 'get_keyword_search_posts' (which returns only posts).

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 provide any guidance on when to use this tool vs alternatives. It lacks context about when to use this versus 'get_keyword_search_posts' or how it relates to 'keyword_search'. No explicit when-to-use or when-not-to-use instructions.

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