mortgage_get_summary

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds 'current' and lists specific data fields, but does not disclose additional behavioral traits such as auth requirements, rate limits, or data freshness. It repeats 'Read-only' which is already in annotations.

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, information-dense sentence that front-loads the purpose ('Get current mortgage balance...') and ends with a clear safety hint ('Read-only'). Every word earns its place; no redundancy beyond the redundant but short safety annotation.

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?

With no input parameters and no output schema, the description lists all key data elements (balance, rate, payment, due date, escrow summary) providing a clear picture of what to expect. It does not mention prerequisites like active login, but given sibling tools (mortgage_start_login) and the read-only nature, the description is sufficiently complete for a simple summary 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?

The tool has zero parameters and the schema is trivially fully covered. There is no need for parameter documentation, so the baseline of 4 applies. The description correctly focuses on the resource and output content rather than parameters.

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 retrieves a 'current mortgage balance, rate, payment, due date, and escrow summary' with a specific verb 'Get' and resource. It distinguishes itself from siblings like mortgage_get_payment_history (history) and mortgage_get_escrow (escrow-only) by providing a comprehensive snapshot.

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 implies usage for obtaining the current mortgage overview and notes it is read-only. It does not explicitly mention alternatives or exclusions, but the 'current...summary' wording and sibling context make the intended use clear. No explicit when-not-to-use guidance is provided.

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