banking_compliance__buffer_check

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

With no annotations and a minimal description, the tool's behavioral characteristics (return type, side effects, authentication needs, thresholds) are completely undisclosed. The description adds no value beyond the 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?

Extremely concise (7 words) but due to under-specification, not efficiency. The description does not earn its brevity; a 5-parameter banking tool needs at least a sentence clarifying inputs and outputs.

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 tool's moderate complexity (5 parameters, banking domain), the description is wholly incomplete. No output type, no parameter semantics, no behavioral context, and no guidance among siblings. The agent cannot effectively select or use this tool.

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 provides no parameter explanations. For a 5-parameter tool, this is severely inadequate—e.g., 'dsib' and 'minimum' are undefined, leaving the agent guessing their meaning and required input range.

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 is a tautology: '[banking-compliance] buffer_check' merely restates the name with a prefix, offering no explanation of what the tool does (e.g., checking capital buffers against minimum requirements). The parameter names hint at CET1 ratio and buffers (conservation, countercyclical, DSIB surcharge), but no explicit purpose is stated.

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 usage guidance is provided. The description fails to indicate when to use this tool versus sibling tools like 'capital_ratio', 'lcr', or 'leverage_ratio' (e.g., for buffer adequacy vs. core ratio computation).

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