keyso_get_report_group_organic_sitepages_rid

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

With no annotations, the description carries the full burden of behavioral disclosure. It does disclose that the operation is a GET and provides the exact path and a concrete example URL, signaling a read operation, but it omits authentication needs, rate limits, error behavior, response shape, or pagination behavior.

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 logically ordered: human-readable title, method, path, then example. It contains no filler, though its brevity limits the depth of the guidance it provides.

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 GET endpoint with seven parameters and no output schema, this description is thin. It does not explain the report-group concept, how to obtain or validate rid, what fields the response contains, or how this endpoint differs from the simple organic sitepages variant.

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%, so the baseline is 3. The description's example URL reinforces how sort, page, and per_page are used, but it does not add meaning beyond the schema descriptions for rid, filter, token, or base_url.

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 names the resource ('Органическая выдача - страницы группы') and gives the HTTP method and full path, which together identify this as a GET for organic site pages inside a report group. It is clear but does not distinguish the tool from siblings like keyso_get_report_group_organic_keywords_rid or keyso_get_report_simple_organic_sitepages.

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 versus the many related report-group or simple-report endpoints. There is no mention of prerequisites, such as having created a report group, or of alternatives for simple organic sitepages.

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