get_cdps_by_address

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 but only states it retrieves 'all' CDPs. It fails to specify error handling (e.g., invalid address format), return structure, pagination behavior, or whether the operation is read-only.

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 redundant words. It immediately conveys the core function without unnecessary preamble or filler.

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 tool's simplicity (one string parameter with full schema coverage) and lack of output schema, the description is minimally adequate. However, it could be improved by clarifying what constitutes a CDP in this context or noting the relationship to the sibling 'by_owner' variant.

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 input schema has 100% description coverage, documenting the bech32 address format. The description mentions 'specific Cardano address' but adds no semantic details beyond what the schema already provides (such as examples or validation rules), warranting 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 the action (Get) and resource (CDPs/loans) scoped to a specific Cardano address. However, it does not explicitly differentiate from the sibling tool 'get_cdps_by_owner', leaving ambiguity about when to use address versus owner lookup.

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 like 'get_cdps_by_owner' or 'get_all_cdps'. The description lacks when-not-to-use conditions or prerequisites for the address parameter.

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