mortgage_get_escrow

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds only 'Read-only', which repeats the annotation. It does not disclose any additional behavioral traits such as whether escrow data may not exist, whether it requires an active login, or what the response structure looks like. With strong annotations, the description adds minimal value beyond them.

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 two short sentences: 'Get current escrow information. Read-only.' It is front-loaded with the action and resource, with no unnecessary words. 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?

For a zero-parameter, read-only operation, the description states what it retrieves (current escrow information). However, it omits details about the return format or edge cases (e.g., no escrow account). Given the lack of an output schema and the simple nature of the tool, this is mostly adequate but not exhaustive.

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 input schema is an empty object. The description correctly implies no inputs are needed. Per the rubric, baseline is 4 for zero-parameter tools. The description adds no param semantics because there are none.

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 uses the specific verb 'Get' with the resource 'current escrow information', clearly distinguishing it from sibling tools like mortgage_get_summary and mortgage_get_payment_history. No ambiguity about what the tool does.

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 explicit guidance on when to use this tool vs alternatives. The resource name makes the use case obvious, but there are no exclusion criteria or pointers to alternative tools. The simplicity implies usage, but the description doesn't state it.

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