koios_param_updates

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

No annotations are present, and the description provides no additional behavioral context such as pagination behavior, output format, data scoping, or any side effects. It only restates the essential purpose, leaving the agent without insights into how the endpoint behaves beyond the literal request.

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, focused sentence with no wasted words. It is front-loaded with the action and resource, making it easy to parse.

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 additional context given the absence of an output schema and annotations. It would benefit from mentioning typical response fields or clarifying that it returns a list of proposals. However, for a simple, parameterized query endpoint, the minimal description is moderately acceptable.

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 schema descriptions cover all four parameters (limit, order, offset, select) with sufficient detail, so the tool description need not explain them. The description adds no parameter-level meaning, but the schema already provides adequate semantics, yielding the baseline score.

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 clearly states a specific action ('Get') and resource ('protocol parameter update proposals') with a context qualifier ('submitted on-chain'). This distinguishes it from related endpoints like koios_cli_protocol_params, which likely returns current parameters, not proposals.

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?

No guidance is provided on when to use this tool versus alternatives. Sibling tools include koios_cli_protocol_params, but the description does not differentiate or recommend when to choose this endpoint. The usage is implied by the purpose but not explicitly stated.

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