text_remove_line_numbers

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

With no annotations, the description carries the transparency burden. It mentions intelligent pattern detection and support for various numbering formats, but does not disclose behavior for missing line numbers, input requirements, or error scenarios. It's adequate but not comprehensive.

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 includes redundant elements like 'Menu ID: remove_line_numbers' and repeats 'Remove Line Numbers'. While relatively short, it wastes space on a mention of describe_tool. Could be more focused.

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 zero parameters, no output schema, and no annotations, the description is incomplete. It does not explain how to invoke the tool (what input to provide) or what to expect in return, leaving significant gaps for an agent.

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 input schema defines no parameters (additionalProperties: true), yet the tool clearly needs some input text. The description fails to explain how to provide the text or any configurations. With no parameters in schema, the description should compensate but does not.

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 it removes line numbers from text with intelligent pattern detection, specifying the action and resource. It distinguishes from sibling 'text_add_line_numbers' by being the reverse operation, but doesn't explicitly differentiate from other text manipulation tools.

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 like 'text_add_line_numbers' or other text tools. It merely suggests using describe_tool for full guidance, which shifts responsibility and provides no immediate context.

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