predictive_burn_rate__net_burn

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

With no annotations and only a minimal description, there is no disclosure of behavioral traits such as whether the tool is read-only, has side effects, or requires specific permissions. The description carries the full burden but fails to provide any behavioral context.

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?

While the description is short, it is not effectively concise because it omits essential information. It is underspecified rather than cleanly conveying core purpose. A score of 2 acknowledges the lack of verbosity but penalizes the failure to convey meaning.

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 absence of annotations, output schema, and any parameter descriptions, the description is grossly incomplete. For a tool with two required parameters and no other context, the description must provide more information to enable correct 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?

The input schema has two parameters with no descriptions, and schema description coverage is 0%. The description adds no meaning to the parameters 'gross_outflows' and 'collections', leaving the agent without any semantic guidance beyond the parameter names.

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 a tautology, merely repeating the tool name 'net_burn' within brackets. It does not state what the tool does, such as calculating net burn rate from gross outflows and collections. This provides no clarity for an AI agent to understand the tool's purpose.

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 guidelines are provided. The description does not mention when to use this tool versus similar siblings like 'predictive_burn_rate__simple_runway' or 'predictive_burn_rate__growth_adjusted_runway', leaving the agent without context for selection.

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