insert_blockquote

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

With no annotations, the description adds value by specifying formatting details (720-twip left indent and italic formatting). It does not cover side effects, permissions, or error scenarios, but the disclosed behavior is concrete and useful.

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 concise, with a clear main sentence followed by one additional formatting detail and a bullet list for parameters. Every sentence serves a purpose without unnecessary fluff.

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's simplicity (2 parameters, clear purpose) and the presence of an output schema, the description covers essential aspects. It could mention return behavior or error handling, but is largely complete for an insertion tool.

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% description coverage, but the description's Args section explains both parameters: para_id identifies the reference paragraph for insertion, and text provides the blockquote content. This fully compensates for the missing schema descriptions.

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 'Insert a blockquote paragraph after the given paragraph,' specifying a verb and resource. It uniquely identifies the tool among siblings (e.g., insert_paragraph, insert_code_block) by focusing on blockquote insertion.

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 implies usage for inserting blockquote paragraphs after a reference paragraph, but it does not provide explicit guidance on when to use this tool versus alternatives like insert_paragraph or insert_text_box. No exclusions or when-not conditions are mentioned.

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