list_search_keyword

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds only the endpoint path and parameter names, with no additional behavioral context such as pagination behavior, result limits, or response semantics.

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 compact and front-loaded with the purpose, followed by the endpoint and an Args block. It wastes no words, though the available space could have been used to add more useful semantic or usage details.

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?

For a simple read-only GET endpoint with two optional parameters and an output schema, the essential call contract is mostly present. However, the description does not clarify what kind of keywords are searched or how pagination works, leaving some ambiguity for an agent selecting or invoking the tool.

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 0%, so the description needed to compensate, but it only repeats 'query' and 'page' as 'Query parameter.' This adds minimal meaning beyond the schema property names and does not explain what values are expected or how the parameters affect the search.

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 ('Search for keywords') and identifies the resource via the endpoint 'GET /api/v1/search/keyword'. It is clear enough on its own, though it does not explicitly differentiate this from sibling search tools like list_search or list_search_company.

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?

There is no guidance about when to use this tool versus alternatives such as list_search, list_search_company, or get_keyword_by_keyword_id. The description only lists parameters and provides no selection criteria or exclusions.

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