add_bullet_list

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

No annotations provided, so the description carries full burden. It only states 'add' without disclosing whether the list appends or overwrites, what happens to the document, or any side effects. No behavioral traits beyond the action are revealed.

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 very concise (one short phrase), but it sacrifices necessary detail. For a tool with 4 parameters and no annotations, this level of conciseness is under-specification rather than efficient communication. Every sentence should earn its place, but here the single sentence is insufficient.

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 4 parameters, no output schema, and no annotations, the description is completely inadequate. It does not specify preconditions (e.g., does the document exist?), postconditions, or return values. The agent lacks critical context to use this tool safely or correctly.

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 description coverage is 0% and the description adds no meaning to parameters. It does not explain that 'items' are the bullet points, nor the purpose of 'font_name' and 'font_size'. With 4 parameters (2 required), the agent receives no guidance on how to use them effectively.

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 bulleted list' is clear but vague. It does not specify the context (e.g., adding to a document) or distinguish from siblings like 'add_heading' or 'add_paragraph' sufficiently. With sibling names suggesting document operations, the purpose is implied but not explicit.

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 on when to use this tool versus alternatives. The description lacks context for when a bulleted list is appropriate compared to headings, paragraphs, or other list types. No explicit exclusions or recommendations.

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