prepend_block

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

All annotations are false, indicating no safety hints. The description does not disclose behavioral traits such as error handling, atomicity, or permission requirements. For a mutation tool, more transparency is needed. No contradiction with annotations.

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, concise sentence that conveys the core purpose. It is front-loaded and contains no redundant information, earning a high conciseness score.

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 no output schema and no annotations, the description lacks important context like return value, error conditions, prerequisites (e.g., parent block existence), and behavior in edge cases. This makes it incomplete for an agent to use confidently.

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 input schema has 100% description coverage, so the schema already documents parameter meaning. The description adds no additional semantics beyond what is in the schema, meeting the baseline of 3.

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 action: inserting a child block at the beginning of the parent block. It uses a specific verb ('prepend') and resource ('block'), and distinguishes itself from siblings like append_block (insert at end) and insert_block (insert at arbitrary position).

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 compared to alternative insertion tools (insert_block, append_block, batch_insert_blocks). The description does not mention prerequisites, constraints, or best practices.

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