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

No annotations are provided, so the description must fully disclose behavior. It describes core functionality but omits details like input format requirements, error handling, and the structure of the parsed output. As a parse tool with no output schema, the agent lacks critical behavioral information.

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 very concise (one sentence), but it lacks structural elements like usage notes or examples. While it front-loads the verb, the brevity sacrifices clarity for a tool that parses a specific format.

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 tool that parses a non-trivial format (unified diff), the description is severely incomplete. No output schema, no input format details, and no error handling information. The agent cannot reliably use this tool based solely on the description.

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 single parameter 'text' has 0% schema description coverage and no extra explanation in the tool description. The agent is given no additional meaning, such as expected format (e.g., 'must be valid unified diff text') or encoding hints.

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 the tool's action ('Parse') and resource ('unified diff'), and mentions specific outputs ('files changed, lines added/removed'). It differentiates from the sibling 'text_diff' which computes diffs rather than parsing them.

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?

The description provides no guidance on when to use this tool versus alternatives, such as 'text_diff'. There is no mention of prerequisites 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.