mortgage_get_payment_history

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

The description adds no behavioral context beyond what annotations already provide. It only restates 'Read-only' which is redundant with readOnlyHint=true. It does not describe the return format, whether history is chronological, or that the 'months' parameter limits the range.

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 extremely concise with two short sentences. It is front-loaded with the action and resource, and the 'Read-only' addition, while redundant, does not add bulk. 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?

The tool has one parameter and no output schema, yet the description does not explain what the payment history includes or how 'months' affects the result. Annotations cover safety but not usage semantics, leaving the description incomplete for a straightforward but under-specified tool.

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 description coverage is 0%, so the description must compensate for the 'months' parameter. It does not mention 'months' at all, leaving its meaning ambiguous. Even though the schema shows type and constraints, the description adds no semantics about what the parameter controls.

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 gets mortgage payment history, with a specific verb and resource. The resource name itself distinguishes it from siblings like mortgage_list_statements and mortgage_get_summary, so the purpose is unambiguous.

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 description provides no guidance on when to use this tool versus alternatives. It does not mention any preconditions, exclusions, or why an agent might prefer this over mortgage_list_statements or mortgage_get_summary.

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