Get HSA account details

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

Annotations already declare readOnlyHint=true, so the description need not repeat safety. It adds value by disclosing a 404 error for non-US users, which is actionable error-prevention context beyond the annotation.

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?

Two short sentences carry both the core purpose and an error condition, both front-loaded. No filler or redundant restating of the 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 simple read-only tool with one optional param and an output schema, the description covers the main behavior and a key failure mode. The optional workspace_id is self-explanatory; nothing critical 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?

Schema coverage is 100% and the single param workspace_id is already described in the schema. The description adds no extra parameter guidance, so baseline 3 is appropriate when the schema fully covers semantics.

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 states the exact resource ('Health Savings Account details') and scope ('US HSA'), and the verb 'Fetch' is unambiguous. It also differentiates from the sibling get_hsa_investments by implying details, not investments.

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 specifies a condition ('May 404 for non-US users'), which effectively tells the agent to use it for US users. It does not explicitly name alternatives like get_hsa_investments, but the purpose is clear enough to direct selection.

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