get_keyword_search

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the return data but doesn't cover critical aspects like whether this is a read-only operation, error handling, rate limits, or authentication needs, which are essential for a tool that retrieves search results.

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, efficient sentence that front-loads the purpose and return values. It avoids unnecessary details, though it could be slightly more structured by explicitly separating the action from the output.

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 no annotations and no output schema, the description is incomplete for a tool that returns multiple data types (status, analytics, posts). It lacks details on response structure, error cases, or behavioral traits, leaving significant gaps for the agent to handle.

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 100%, so the input schema already documents the 'id' parameter as a positive integer. The description adds no additional meaning beyond this, such as explaining where to obtain the ID or its format, but meets the baseline for high schema coverage.

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 action ('Get results') and resource ('keyword search by ID'), specifying what data is returned (search status, analytics summary, and posts). However, it doesn't differentiate from sibling tools like 'get_keyword_search_posts' or 'keyword_search', which likely serve related functions.

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?

No guidance is provided on when to use this tool versus alternatives. With siblings like 'get_keyword_search_posts' and 'keyword_search', the description lacks context on prerequisites, such as needing an existing search ID, or exclusions, leaving the agent to infer usage.

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