mortgage_list_statements

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, but the description adds valuable context beyond these: it explicitly states that the tool does not download statements without a later explicit implementation. This clarifies behavior for the agent, making the tool's non-download behavior transparent.

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 highly concise and front-loaded: 'List available mortgage statements' is the first sentence, followed by a single clarifying sentence about read-only behavior. No wasted words; every part adds value.

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?

For a simple list tool with one optional parameter and no output schema, the description covers the main purpose and read-only behavior sufficiently. However, it omits any mention of the year filtering or what the returned statements will look like, leaving a small but notable gap in completeness.

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 has one optional 'year' parameter with a range, but the description does not explain its purpose or behavior (e.g., filter by year, omit to get all). With 0% schema description coverage, the description should compensate by explaining the parameter, but it doesn't, leaving the agent to infer from the parameter name alone.

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 tool 'lists available mortgage statements,' specifying a concrete action and resource. It distinguishes itself from siblings like mortgage_get_payment_history and mortgage_get_escrow by focusing on statements, and the additional note about not downloading clarifies its exact scope.

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?

The usage context is implied: use this to see what statements are available. However, there is no explicit guidance on when to use this versus other mortgage tools, or what to do if you need to download a statement. The read-only note hints at its non-downloading nature but doesn't provide exclusions or alternatives.

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