get_active_page_preview_blocks

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

Annotations are absent, so the description must convey behavior. It only says 'get list', implying a read operation, but offers no detail on output shape, pagination, or limitations. The existence of an output schema partially covers return values, but the description adds no behavioral nuance.

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 brevity is not helpful here—it under-specifies. While the single sentence is structured, it omits essential context that could be added without bloat.

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 one-parameter tool with many siblings, the description is incomplete. It does not explain what a 'page preview block' is, when to use it, or how the parameter is interpreted. The presence of an output schema mitigates some need for return-value detail, but the purpose and usage gap remains significant.

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%, and the description never mentions site_url. The agent only has the parameter name, which is somewhat self-explanatory but lacks format or expected value details. The description adds zero parameter guidance.

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 verb 'get' and resource 'list of active page preview blocks', so it's clear it retrieves data. However, it doesn't distinguish from siblings like get_deep_link_blocks, and 'page preview blocks' is not elaborated, leaving ambiguity.

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 the many sibling get_* tools. No exclusions, prerequisites, or context to help an agent choose this over alternatives.

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