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

With no annotations, the description carries the full burden of behavioral disclosure, but it only describes what data the book contains rather than how the tool behaves. It does not state whether the data is a live snapshot, whether calling is read-only, whether permissions are needed, or what the response format is. The only behavioral hint is the daily 18:00 UTC payout timing embedded in the content list.

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 entire description is a single front-loaded sentence that names the resource first and then lists its key components in one breath. There is no filler, repetition, or buried context. It is compact while preserving the important 18:00 UTC payout detail.

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 no-parameter, no-output-schema status tool, the description covers the main informational needs: what the book is, what components it reports on, and the payout schedule. It does not describe the response structure or format, but that is less critical given the simple nature of the tool. The main missing piece is usage/selection context, which is already accounted for under usage_guidelines.

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 tool has zero parameters, so there are no parameter semantics to document. The schema is empty and the description appropriately focuses on what data the tool exposes. This exceeds the baseline for a no-parameter tool because it clarifies the meaning of the returned status components.

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 identifies the resource precisely as the protocol-owned liquidity book and enumerates its contents: value, positions, fees collected, pending payout, and paid LOOM. This clearly differentiates it from sibling tools like my_positions and list_pools. It lacks an explicit action verb such as 'get' or 'list', but the tool name and title make the status semantics reasonably clear.

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 gives no guidance on when to use this tool instead of get_pool, list_pools, my_positions, or quote_position. It does not state prerequisites, exclusions, or a recommended selection path. An agent must infer from the resource name that this is the protocol-level book view.

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