get_vault_collaterals

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

No annotations are provided, so the description must carry the full burden. It only mentions 'Public REST', implying a read-only public endpoint, but fails to disclose pagination, response format, or whether this is a snapshot or a dynamic configuration.

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 concise fragment, but it is not a complete sentence and omits a verb. It wastes no words but leaves out essential context that a full sentence could provide.

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?

Given the presence of many closely named sibling tools and no output schema, the description is incomplete. It does not explain what constitutes a 'configuration list' or how this tool differs from get_collateral_history, get_latest_collateral, or get_public_protocol_overview.

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 the input schema fully covers the parameter surface. The description adds no parameter info, but with zero params the baseline is 4.

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 as a list of vault collateral configurations, but it lacks a clear verb and does not distinguish this from sibling tools like get_latest_collateral or get_chain_collateral_history. The phrase 'vault collateral configuration list' is essentially a restatement of the tool name.

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. The description does not mention any exclusions, alternatives, or context, leaving the agent to guess how it differs from other getter tools.

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