add_bullet_points

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

No behavioral annotations are provided, so the description carries the full burden. 'Add bullet points to a placeholder' only conveys a write operation; it does not explain whether existing content is replaced or appended, what happens if the placeholder is empty, or what side effects occur. This is a minimal mutation description with no behavioral depth.

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 short sentence with no fluff or redundancy. It is concise and front-loads the core action, though it is arguably too sparse to fully support correct invocation.

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?

With 4 parameters, 0% schema description coverage, no behavioral annotations, and a large set of sibling tools, this description is far from complete. It omits how the placeholder is identified, what the presentation_id does, and how this relates to alternative text/placeholder tools. The output schema exists, so return format explanation is not required, but essential invocation context is missing.

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%, so the description must compensate. It loosely maps to the bullet_points and placeholder_idx parameters, but it does not explain slide_index, presentation_id, or the expected format of the bullet_points array. The description adds minimal meaning beyond the parameter names.

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 states a specific action ('Add bullet points') applied to a specific resource ('placeholder'), which is immediately understandable. However, it does not explicitly distinguish this from sibling tools like populate_placeholder or manage_text, so clarity is strong but differentiation is absent.

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?

There is no guidance on when to use this tool versus alternatives such as populate_placeholder or manage_text. The intended use is only implied by the name and short phrase; no exclusions, prerequisites, or contextual conditions are provided.

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