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

Beyond the annotations (readOnlyHint, openWorldHint, destructiveHint), the description discloses significant behavioral traits: the output format is decimal-string rupees, the summary covers the full filtered set and ties the spreading reconciliation, no target-level split or source transactions are returned, page tokens are source-pinned and expiration behavior is described, and run-state fields (known_stale, not_assessed) are explained. This far exceeds the annotation coverage and gives the agent a precise mental model of the tool's behavior.

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 compact and information-dense. It leads with 'MANAGEMENT data class' and a clear statement of purpose, then efficiently layers in the data model, filtering, paging, summary behavior, and run-state semantics across four sentences. Every sentence adds unique information, and there is no filler or repetition of the schema.

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?

For a complex tool with 6 parameters, no output schema, and no nested objects, the description is remarkably complete. It explains the output grain, the arithmetic relationship of figures, filtering options, paging behavior, what data is excluded, and how to interpret run-state flags. It leaves no major ambiguities about what the tool returns or how to handle pagination edge cases, making it fully self-sufficient for the agent.

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 covers all 6 parameters with descriptions (100% coverage), so the baseline is 3. The tool description adds semantic value by explaining the data context (books + spreading = MIS, decimal-string rupees), which helps understand parameters like min_abs_mis. It also clarifies the interaction between filtering and paging, and reinforces the source-pinned nature of page_token. While it doesn't describe each parameter individually, the holistic context meaningfully aids parameter understanding, so a 4 is justified.

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 states a specific verb ('Read') and a specific resource ('the current persisted allocation run at account grain'), and explicitly clarifies the data model (books + spreading adjustment = MIS figure). It distinguishes itself from the sibling get_allocation_target_figures by noting that no target-level split is returned, making the purpose unmistakable.

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 provides clear context for when to use this tool: it reads management allocation data at account grain, supports filtering before paging, and clarifies that target-level splits are excluded. It also gives explicit paging guidance (restart at page 1 if source_changed) and explains how to interpret run-state flags. However, it does not name a direct alternative tool or state explicit 'when not to use' conditions, so it stops short of a 5.

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