revenue_recognition__contract_liability

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

No annotations are provided, so the description carries full burden for behavioral disclosure. The description is a mere noun phrase and reveals nothing about side effects, idempotency, authentication needs, or output behavior. The agent has no clue what happens when this tool is called.

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 concise (one phrase) but at the expense of being useless. It does not earn its place because it communicates almost nothing beyond the tool name. True conciseness should pack meaning efficiently, not omit 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?

The tool is part of a revenue recognition suite with complex accounting concepts. Given no output schema, minimal parameters, and a domain that typically requires context (e.g., what is the contract liability? How is it derived?), the description is completely inadequate for enabling correct usage.

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%, so the description must compensate. It adds zero meaning to the parameters 'billed' and 'recognized'. The relationship between these numbers (e.g., subtraction to get liability) is not hinted. The agent gets no help understanding how to set these parameters correctly.

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 provides a domain label but no verb or action; it is a noun phrase that vaguely indicates the tool is about contract liability in revenue recognition, but does not specify whether it calculates the liability, adjusts it, or reports it. It fails to distinguish from siblings like allocate_transaction_price or over_time_revenue.

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. The description does not mention context, prerequisites, or exclusion criteria. Zero actionable information for an AI agent to decide when to invoke this tool.

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