seodata_get_page

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

With no annotations, the description carries the full behavioral burden. The only behavioral disclosure is 'Scope: content:read', which indicates a read permission, but the description does not explicitly state read-only behavior, return format, error handling, or any side-effect profile.

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 a single front-loaded sentence plus a short scope note, with no wasted words. It is efficiently structured, though it is arguably too terse given the undocumented parameters.

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 tool with two required parameters, no annotations, and no output schema, the description is incomplete. It identifies the resource and scope but does not clarify parameter usage or what the tool returns, leaving meaningful gaps for an agent invoking it.

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% for two required parameters (storefrontSlug and pageSlug). The description mentions a storefront page but does not explain what the slugs represent, their expected format, or how the two identifiers relate. It adds essentially no parameter meaning beyond the schema.

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 type (a static storefront page) and gives examples, and the tool name supplies the 'get' verb. However, it does not explicitly state that the tool retrieves or returns the page, so the purpose is inferable rather than stated outright. It also does not clearly route the agent away from sibling tools like seodata_get_article.

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 on when to use this tool versus alternatives such as seodata_get_article or seodata_search. The 'Scope: content:read' note hints at required permission but does not explain selection context or exclusions.

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