koios_treasury_withdrawals

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'Get', implying a read operation, but does not disclose pagination behavior, default limits, or what constitutes a withdrawal entry. This is minimally informative but not contradictory.

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 a single, front-loaded sentence with no filler or redundancy. It is appropriately short for a simple read operation, though slightly repetitive with 'treasury' appearing twice.

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?

The description conveys the core purpose but lacks context such as pagination defaults, response format, or the distinction from reserve withdrawals. Given the four schema-documented parameters and no output schema, more detail would improve selection confidence, yet the essential action is clear.

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?

All four parameters are already described in the input schema (100% coverage), so the description does not add parameter-level meaning. It correctly implies a paginated query through the schema's limit/offset descriptions, but the description itself contributes nothing beyond the schema.

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 a specific verb ('Get') and clearly identifies the resource ('treasury withdrawals from the Cardano treasury'). However, it does not distinguish this from the closely related sibling tool `koios_reserve_withdrawals`, so it falls short of full clarity.

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 about when to use this tool versus alternatives, especially the sibling `koios_reserve_withdrawals`. The description gives no context for selecting between them, and no exclusions or prerequisites are mentioned.

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