company_revenue

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

No annotations are present and the description does not disclose side effects, read-only vs. mutating behavior, or any operational impact. The phrase 'inspect, plan or supply' leaves it unclear whether the tool performs reads, writes, or both.

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 short and structurally simple, but the wording is convoluted and semantically unclear. It is concise in length yet fails to communicate a clear function.

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?

Despite an output schema being indicated, no parameter details or behavior are explained. The description is inadequate for an agent to understand what inputs to supply or what outcome to expect.

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?

None of the seven parameters are described, and the description provides no hints about what 'now', 'engine', 'operation', 'entity_ref', 'bundle_json', or 'payload_json' mean. Required parameters project_id and bundle_json are mentioned nowhere.

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 gives a verb and a resource ('inspect, plan or supply sealed revenue receipts') but the resource is vague and the multiple verbs make the actual purpose unclear. It does not distinguish this tool from numerous other company_* financial tools like company_receivables or company_spend.

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?

There is no guidance on when to use this tool instead of any sibling tool. No context, preconditions, or examples are provided to help select it appropriately.

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