insert_line_or_paragraph_near_text

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

No annotations provided, so description carries full burden. It mentions 'insert' but fails to disclose if it modifies the document in-place, requires specific permissions, or what happens if target_text is not found. Behavioral traits are not 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?

Extremely short, but this is under-specification rather than conciseness. The single sentence lacks critical details and does not earn its place by being informative.

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 5 parameters and no output schema, the description is grossly incomplete. It does not explain the insertion behavior, the meaning of 'near', or the interaction between parameters. Essential context for correct usage is absent.

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%, yet the description adds no meaning to any parameter. It doesn't explain 'target_text', 'line_text', 'position', or 'target_paragraph_index'. The phrase 'near the found text' vaguely hints at target_text but without clarification.

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?

Description states it inserts a line or paragraph near found text, which is a specific verb-resource combo. However, it's vague about what constitutes a 'line/paragraph' and doesn't clearly distinguish from similar siblings like 'insert_text_at_paragraph' or 'insert_numbered_list_near_text'.

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 doesn't mention prerequisites, context, or when not to use it.

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