listRevenuePostings

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

No annotations are provided, so the description bears full burden. It states pagination and filtering but does not disclose whether the operation is read-only, any authentication requirements, rate limits, or potential side effects. The description is insufficient for a tool with no annotations.

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 two sentences long, with no superfluous words. The first sentence defines the action and resource, the second lists key filters. Perfectly concise and front-loaded.

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?

With 12 parameters, no output schema, and no annotations, the description is too brief. It fails to explain pagination mechanics, default ordering, maximum limit, or the meaning of the journal_entry_id__isnull parameter. The response format is not described, leaving the agent underinformed.

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 100%, so the baseline is 3. The description reiterates that filtering is available by contract, revenue contract, etc., but adds no new meaning beyond the schema. The parameters are well-described in the schema, so the description does not improve understanding.

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 uses specific verb 'Retrieve a paginated list' and clearly identifies the resource as 'revenue postings', with a parenthetical explanation of what they are. It distinguishes the tool from siblings like listContracts and refreshRevenuePostings by focusing on listing revenue allocations.

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?

The description mentions filtering capabilities but does not explicitly state when to use this tool versus alternatives or when not to use it. The context is implied by the resource name, but no usage restrictions or prerequisites are given.

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