docs_insert_bullets

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

No annotations exist, so the description carries the full burden. It does not disclose behavioral traits such as whether existing bullet formatting is replaced or toggled, how start_index and end_index map to paragraphs, or any side effects. The description only states the action without contextual detail.

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 with no fluff. It is efficiently structured and front-loaded, but the brevity comes at the cost of omitting necessary details for correct usage.

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?

For a tool with 4 parameters, no annotations, and no output schema shown, the description is too thin. It fails to explain parameter meanings, bullet_type options, or the expected behavior when applying formatting to a range. The description is not sufficient for an agent to use the tool effectively.

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, and the tool description provides no parameter semantics. It does not explain that start_index and end_index refer to character offsets, what bullet_type accepts (beyond a default value), or the role of document_id. The description adds no value for parameter understanding.

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 tool's function: 'Apply bullet or numbered list formatting to paragraphs in a Google Doc.' It uses a specific verb and resource, distinguishing it from sibling tools like docs_insert_paragraph (which inserts new paragraphs) and slides_insert_bullets (which works on slides).

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 versus alternatives like docs_set_paragraph_style or docs_format_text. The description implies usage for list formatting but does not state when it should be preferred or excluded.

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