refreshRevenuePostings

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

With no annotations, description carries full burden. It discloses mutation ('recalculate and upsert') and approval workflow. However, it lacks details on side effects, error behavior, or success/failure outcomes.

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?

Two concise sentences, no fluff. Action and key behavioral note are front-loaded. Every sentence adds value.

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 no output schema, description covers core functionality, required parameters, and a key behavioral detail (approval gate). Sufficient for an agent to use correctly, though return values are unaddressed.

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 coverage is 100% with parameter descriptions. Description adds that backend rejects partial inputs, which provides context beyond schema. Baseline 3 is appropriate as description adds marginal value.

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 uses specific verb ('Recalculate and upsert') and resource ('revenue postings'), clearly scoped to a specific revenue contract item/performance obligation at a given date. This distinguishes it from siblings like listRevenuePostings or recogniseRevenue.

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?

Explicitly states that all five identifiers are required and that partial inputs are rejected. Also instructs not to ask for re-confirmation because host enforces approval gate. Provides clear constraints but does not contrast with alternatives explicitly.

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