finance_financial_advice_mortgage_finance_ca

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

Annotations indicate destructiveHint=true and readOnlyHint=false, but the description does not disclose side effects, mutation, or what the action may change. It only mentions routing and scoping, providing little behavioral context beyond the 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 reasonably concise and front-loads the primary purpose. It avoids unnecessary verbosity while including key routing and parameter information, though some boilerplate phrasing could be trimmed.

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 description leaves important context unexplained: what mortgage finance action does, what outcomes to expect, what the output schema contains, and when this tool should be selected from the large sibling set. It is sufficient only as a generic wrapper description.

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 0% description coverage, but the description adds brief meanings for both parameters: 'message' is a free-text objective and 'inputs' is an optional JSON string. This is helpful but lacks detail on expected structure, allowed values, or examples.

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 verb ('Run') and the specific resource ('the finance domain agent action financial_advice_mortgage_finance_ca'), making the tool's immediate purpose identifiable. It does not, however, explain what mortgage finance advice entails, which limits full clarity.

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 gives no guidance on when to use this tool versus any alternative, aside from noting it routes through a domain-agent dispatcher. There is no mention of scenarios, prerequisites, or conditions that would make this tool appropriate or inappropriate.

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