get_all_cdps

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

No annotations provided, so description carries full disclosure burden, yet fails to mention this is read-only (implied only by 'Get'), doesn't describe return format, pagination behavior, or maximum result limits. Omits that this queries protocol state which may change between calls.

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?

Single 9-word sentence is appropriately front-loaded with the core action, but given the complete lack of schema descriptions and annotations, it is underspecified rather than optimally concise. Omits essential context that cannot be found elsewhere.

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?

Inadequate for a complex DeFi protocol tool with no annotations, no output schema, and undocumented input parameters. Fails to explain what constitutes a CDP in this context, return data structure, or the necessity of pagination given the 500-item limit constraint in schema.

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?

With 0% schema description coverage, the description only partially compensates by mentioning the 'iAsset' filter (mapping to the 'asset' parameter) but completely ignores the critical pagination parameters 'limit' and 'offset' necessary for retrieving large datasets from this 'get all' operation.

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 specific verb 'Get' and resource 'CDPs/loans' with scope modifier 'all', distinguishing it from sibling tools like 'get_cdps_by_address' and 'get_cdps_by_owner' which target specific subsets. The synonym 'loans' adds clarity for domain terminology.

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 explicit guidance on when to use this broad query versus the filtered siblings (get_cdps_by_address/get_cdps_by_owner). Mentions optional filtering by iAsset but doesn't explain pagination requirements or when results might be too large for single calls.

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