debt_restructuring__haircut_pct

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

No annotations are provided, and the description contains no behavioral information. It does not disclose whether this tool is a calculation, what side effects it has, or any other behavioral traits. The description adds zero value beyond the tool name.

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 extremely short (one phrase), but it sacrifices substance for brevity. Every word is necessary but insufficient. It is not a model of conciseness because it omits essential information.

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 lack of annotations, output schema, and the presence of many sibling tools, the description is critically incomplete. An agent cannot determine what this tool computes, when to use it, or how to interpret its parameters. It provides no context for effective selection or invocation.

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 does not explain the two parameters (face_value, new_value). It provides no context on what these values represent or how they relate to each other. The description fails to add meaning beyond the input schema.

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 is only a prefix and name ('[debt-restructuring] haircut_pct'), which is essentially a tautology. It does not state what the tool does, lacking a verb or resource clarification. For domain experts it may hint at calculating a haircut percentage, but it's vague and does not distinguish from sibling tools like npv_of_terms.

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 such as debt_restructuring__npv_of_terms or debt_restructuring__waterfall. There is no mention of context, prerequisites, or typical scenarios. The description provides no decision support.

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