Paramount Loan Services — Mortgage Loan Application

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered structurally. The description adds the set of returned data categories, which is modestly useful, but says nothing about caching, freshness, or format beyond what the annotations and the no-param schema imply.

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?

A single front-loaded sentence with no filler; the purpose is stated in the first clause and the returned field categories follow. 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 no-parameter, read-only info tool with no output schema, enumerating the returned data categories is adequate for correct invocation. Adding return field names or format would have made it fully complete.

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 takes zero parameters, so there is nothing for the description to disambiguate; baseline for a parameterless tool is 4. The schema is trivially complete and consistent with the description.

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 a specific verb ('Return') and names the resource and its constituent fields (licensing, contact, service area, language details) for a named company. It is unambiguous about what the tool retrieves, though it does not explicitly differentiate itself from the sibling tools.

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?

Usage is implied rather than stated: an agent can infer this is the discovery tool for company-level facts, distinct from submit_loan_application or list_loan_programs. There is no explicit when-to-use or when-not-to-use guidance, and no alternatives are named.

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

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

Annotations already declare readOnlyHint and openWorldHint=false, so the safety profile is covered. The description adds useful context by saying the returned artifact is the *full* schema including required-field flags, which is more than the annotations provide.

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?

A single front-loaded sentence that states the action first and the value second, with no filler or redundancy.

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 parameters and no output schema, the description does enough by telling the agent what the return value contains (all accepted fields plus required flags). It stops short of describing schema format/size or explicitly tying the call to the submit step, but nothing essential is missing.

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 takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate, and it correctly avoids inventing inputs.

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 a precise verb and resource ('Return the full JSON Schema for a loan application') and clarifies the payoff ('every field the 1003 accepts and which ones are required'). This is inherently distinguishable from the sibling tools, which read company info, list programs, or submit an application.

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 'so you can see...' clause implies the agent uses this to learn the input surface before submitting, but no explicit when-to-use, prerequisites, or alternatives (e.g. submit_loan_application) are named. Usage is left to inference.

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

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

Annotations already declare readOnlyHint=true and openWorldHint=false (a fixed, known catalog), so the safety profile is covered. The description adds useful behavioral context by disclosing the shape of each returned entry (enum value + description), which is not captured anywhere else since there is no output schema.

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?

A single efficiently front-loaded sentence with no filler; the purpose is stated before the detail. The phrasing is slightly garbled ('the loan programs Paramount brokers'), which costs a point but does not obscure meaning.

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 enumeration tool with no output schema, the description covers enough: what comes back and why it matters (the enum value to use in loan.program). It does not say anything about list size or ordering, but nothing essential to calling it is missing.

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 takes zero parameters, so per the rubric the baseline is 4. There is nothing for the description to clarify beyond confirming the call is argument-free.

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 a specific verb (Return) and resource (loan programs) and even says what each entry carries: the enum value for loan.program plus a one-line description. It never names or contrasts the sibling tools, so an agent must infer differentiation from the names alone.

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?

There is no explicit when-to-use or when-not-to-use statement, but the phrase 'the enum value to put in loan.program' strongly implies the tool is consulted before setting that field or calling submit_loan_application. Usage is implied rather than stated.

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

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

Annotations already establish readOnly=false, openWorld=true and non-idempotent. The description adds real behavioral context beyond that: filing triggers a licensed loan officer to contact the borrower, and consent is a prerequisite. It omits the dry_run preview path (left to the schema) and any note on idempotency, so it is strong but not exhaustive.

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?

Four short sentences, front-loaded with the action and counterparty, then the return value, then the follow-up effect, then the disclaimers. Every sentence carries distinct information with no repetition of the name or title.

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 14-parameter tool with nested objects and no output schema, the description covers purpose, consent precondition, side effect, and return value. The dry_run option is described only in the schema, and no error or validation behavior is mentioned, but overall the agent has enough to decide and call correctly.

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 57%, which is mid-range, and the description says nothing about any of the 14 top-level parameters, including the heavily nested loan, borrowers, and property objects. The schema itself is richly annotated, so the baseline of 3 is appropriate, but the description adds no parameter-level meaning of its own.

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 names a specific verb and resource ('File a Uniform Residential Loan Application (Form 1003 / URLA)') with the counterparty and scope ('with Paramount Loan Services on behalf of a borrower'). It also states boundaries ('not a rate quote, a pre-approval or a credit decision') and the return value, so the agent can separate it from get_loan_application_schema and list_loan_programs without ambiguity.

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?

It supplies a precondition ('a borrower who has consented') and rules out adjacent-but-different actions (rate quote, pre-approval, credit decision). It does not point to sibling tools or say when to call get_loan_application_schema first, so it stops short of explicit when-vs-alternatives guidance.

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