indent_text

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

Describes the core behavior (indenting each line) but does not discuss edge cases like empty lines or special characters. No annotations exist, so the description bears full responsibility but remains adequate.

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?

Two sentences plus a parameter list; every word serves a purpose. No fluff or repetition.

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 simple text transformation tool with an output schema, the description covers the essential functionality. Minor omission: does not mention output format or handling of edge cases, but acceptable given simplicity.

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?

All three parameters (text, count, char) are explained with their defaults and roles, adding significant meaning beyond the schema's field names and types. Schema coverage is 0%, so the description fully compensates.

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?

Clearly states it indents each line of text by a specified count of a character, which distinguishes it from sibling tools like pad_text (which adds padding) and wrap_text (which wraps lines).

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 explicit guidance on when to use this vs alternatives, but the purpose is straightforward and easily inferred from the description.

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