insert_numbered_list_near_text

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

No annotations are provided, so the description bears full responsibility for disclosing behavior. It only says 'Create a numbered or bulleted list near text' without explaining effects on existing content, positioning details, or whether the operation is destructive. This is minimal disclosure.

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, but it is too short to provide necessary detail. While it earns its place by stating the main action, it lacks structure and depth, resulting in under-specification.

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 complexity (6 parameters, no annotations, no output schema, many siblings), the description is woefully incomplete. It fails to clarify positioning, list types, or relationship to other list tools, making it difficult for an agent to select and invoke 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 information about any of the six parameters (e.g., doc_id, target_text, list_items, position, target_paragraph_index, bullet_type). The agent has no understanding of how to use these parameters correctly.

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 the verb 'Create' and the resource 'numbered or bulleted list', but the phrase 'near text' is vague and does not differentiate this tool from siblings like insert_list_at_paragraph, insert_list_start, or insert_list_end. The purpose is somewhat clear but not sufficiently specific.

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 the many similar list insertion tools. There is no mention of prerequisites, limitations, or alternative tools, leaving the agent with no decision criteria.

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