add_page_preview_block

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

With no annotations, the description must disclose behavioral traits. It mentions raising BingWebmasterError on failure, but lacks details about idempotency, permission requirements, or effects on existing blocks. The enum values for 'reason' are not explained.

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 brief with a clear structure: purpose, parameter list, and error info. However, it is not self-contained as it omits the 'self' parameter, forcing the agent to infer from the schema. Still, it is efficient for a simple tool.

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 the tool has 4 required params and no annotations, the description should fully enable correct invocation. It misses the 'self' parameter and does not explain the enum for reason. An output schema exists but is not referenced, leaving the agent uninformed about return values.

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?

The schema has 0% coverage, so the description must compensate. It describes site_url, url, and reason, but omits the required 'self' parameter entirely. The reason parameter is described vaguely ('The reason for blocking the page preview') without explaining the enum integer meanings.

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 'Add a page preview block' clearly states the action (add) and the resource (page preview block), distinguishing it from siblings like add_blocked_url or remove_page_preview_block. The verb is specific and the resource is unambiguous.

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., get_active_page_preview_blocks). It only lists arguments and errors, offering no context for decision-making.

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