keyso_get_report_simple_organic_ai_answers

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

With no annotations, the description carries the full burden. It discloses the GET method and that it returns a list, but does not mention response format, pagination behavior, rate limits, or authentication requirements. It is minimal but not misleading.

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 brief, with a clear title and a useful example. It front-loads the core purpose and includes a concrete request example, which is valuable. No wasted words, though it could be more structured.

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 an 8-parameter tool with no output schema, the description is incomplete. It does not explain response structure, pagination defaults, sorting options, or the filter parameter (which only references an external section). The example covers only a few parameters, leaving gaps for an agent to call it correctly.

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 already documents parameters, and the example URL adds practical meaning by showing how base, domain, sort, page, and per_page are used together. This goes beyond the schema's terse 'in: query' descriptions for some fields.

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 tool returns a list of queries where the site was mentioned in AI answers, specifying the AI sources (Yandex Alice, Google SGE). It uses a specific verb and resource. However, it does not explicitly differentiate from sibling report tools, though the AI-answers focus is distinct.

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 on when to use this tool versus alternatives. There is no mention of prerequisites, exclusions, or conditions that would select this over similar report tools. The example URL implies a call pattern but not usage context.

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