Add Single Block

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

With no annotations, the description fully bears responsibility for transparency. It explains non-destructive behavior ('without replacing other blocks'), but does not disclose what happens on failure (e.g., invalid path or blockType) or return value. Adequate but not comprehensive.

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 concise: two sentences and an example. Every part adds value, with the example serving as a quick reference. No wasted words.

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 description covers the core action and parameters, but lacks information about the return value (since no output schema exists). For a tool with 4 parameters and no output schema, additional context about what the tool returns or side effects would be beneficial. Adequate but incomplete.

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 100%, providing a baseline of 3. The description adds clarity by listing the key parameters ('block type, data, and optional position') and providing a concrete example that illustrates usage, which helps the agent understand how to structure the input.

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 it adds a single new block without replacing others, using specific verb 'adds' and resource 'block'. It distinguishes from siblings like 'plone_update_single_block' and 'plone_remove_single_block' by emphasizing it adds rather than updates or removes.

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 specifies when to use ('adds a single new block') and provides an example, but does not explicitly mention when not to use or list alternatives. However, the sibling tools context and the nature of the description make the intended usage clear.

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