get_cdps_by_owner

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

No annotations provided, so description carries full burden. Indicates comprehensive retrieval ('all'), but omits details on error handling (e.g., owner not found), pagination, rate limits, or authentication requirements.

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 efficient sentence with parenthetical detail. Front-loaded with action and resource, zero extraneous text. Every word earns its place.

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?

Adequate for a single-parameter retrieval tool with complete schema coverage. However, lacks description of return value structure since no output schema exists, which would help the agent understand what constitutes a successful response.

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?

Schema coverage is 100% and the parameter description in the schema already documents the owner formats. The description essentially repeats this information without adding syntax examples, validation details, or semantic context 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?

States specific verb ('Get'), resource ('CDPs/loans'), and scope ('for a specific owner'). Differentiates from 'get_all_cdps' by specifying owner-filtering, though it does not explicitly clarify the distinction from sibling 'get_cdps_by_address'.

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?

Implies usage context by specifying accepted input formats ('payment key hash or bech32 address'), but lacks explicit guidance on when to use this tool versus 'get_cdps_by_address' or other retrieval alternatives.

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