keyso_get_serp_id_csv

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

There are no annotations, so the description carries the full burden. It does not disclose what the response format is (CSV), what the boolean flags (searchEngine, organic, context, wizard) do in practice, whether authentication is required, or any rate limits or side effects. The example query only hints at parameter usage.

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 short, but it is under-specified rather than concise. It includes method, path, and an example, but omits essential information about the tool's purpose and behavior. The one-sentence 'parsing result' phrase adds little value.

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?

With 8 parameters, no output schema, and no annotations, the description is inadequate. It does not explain what the CSV contains, how the boolean flags affect the output, how to obtain the 'id', or what the response structure looks like. An agent cannot reliably invoke this tool based on the given description alone.

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 schema already documents all parameters. The description adds no semantic detail beyond the example URL, which shows some boolean values but does not explain their meaning. Baseline 3 is appropriate because the schema handles the heavy lifting.

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 says 'Онлайн парсер выдачи - результат парсинга выдачи' ('Online search results parser - search results parsing result'), which essentially restates the tool name and does not explicitly say it downloads a CSV file for a given SERP ID. It does not differentiate from siblings like keyso_get_serp_id or keyso_get_serp_id_status.

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 about when to use this tool compared to other SERP-related tools. It mentions a path and example query but does not specify which scenarios call for this CSV export instead of JSON results or status checks.

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