get_active_page_preview_blocks

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

No annotations are provided, so the description must fully disclose behavioral traits. It mentions it returns a list and raises an error, but does not state whether the operation is read-only, safe, or requires specific permissions. The description lacks important behavioral context.

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 relatively short but includes non-standard sections like 'Args:', 'Returns:', 'Raises:' which are verbose for a tool description. It could be more concise and front-loaded. The unexplained 'self' parameter adds unnecessary confusion.

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?

Given an output schema exists, the description does not need to detail return values. However, it omits explanation for the 'self' parameter and provides no filtering or pagination context. The tool is simple, but the missing parameter documentation reduces completeness.

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 0%, meaning the description adds no explanation for the two required parameters. It lists 'site_url' in Args but provides no additional meaning. The parameter 'self' is unexplained entirely, leaving the agent with no semantic guidance beyond the schema's type information.

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 clearly states the purpose: 'Get active page preview blocks for a site.' It specifies the action (get) and the resource (active page preview blocks). The mention of 'site_url' as input further clarifies the scope. This distinguishes it from sibling tools like add_page_preview_block or remove_page_preview_block.

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 on when to use this tool versus alternatives. The description merely states what it does, without mentioning prerequisites, exclusions, or when not to use it. Given the many sibling tools, this is a significant gap.

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