Retrieve a paginated page of search URLs for a Yandex Webmaster host using host_id, limit, and offset; results are a sample, not the full index.
Read one page of URLs in search; a sample is not the full index.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| offset | No | ||
| host_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false. The description adds useful pagination/sampling context with 'one page' and 'not the full index', but does not disclose auth requirements, rate limits, ordering, or what the returned URLs represent.
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?
A single front-loaded sentence with no filler. The core purpose comes first, and the sampling caveat is placed immediately after without unnecessary elaboration.
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?
The output schema reduces return-value burden and annotations cover safety, but the description leaves major gaps for a paginated list tool: no host_id guidance, no limit/offset semantics, and no differentiation from many sibling webmaster list tools.
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 must explain parameters, but it names none. 'One page' only vaguely implies limit/offset pagination; the required host_id and the limit/offset defaults remain unexplained.
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?
States a specific verb and resource: 'Read one page of URLs in search.' The clause 'a sample is not the full index' clarifies scope and pagination, but no sibling tool is named to differentiate from other webmaster list endpoints.
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 explicit when-to-use or when-not-to-use guidance and no alternatives named. The 'sample is not the full index' caveat is a caution, not a usage rule, so the agent must infer the tool's appropriate context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.