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

No annotations are provided, so the description carries the burden and does well: it discloses the returned data shape (tier-nested vs tier-agnostic fees/features) and a real behavioral constraint that application_url is a tracked Bancadia link to be passed through verbatim with its query string. It does not state read-only/no-side-effect behavior or auth requirements, which is the remaining gap.

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?

Front-loaded with the core action, then layers detail field-by-field; every sentence carries operational information. It is dense with internal field names (plan_tiers[].fees) but none of it is filler, so the length is earned though slightly heavy.

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 output schema, the description must explain the return shape and it does, including the tier-nesting rule and the tracked-link caveat. For a single-parameter lookup tool this covers everything an agent needs to call it correctly and hand results to a user.

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 schema itself already warns against internal database ids. The description adds pipeline provenance beyond the schema by tying listing_slug to values previously returned by query_business_checking, which helps the agent source the value correctly.

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 and resource ('Get full detail on one specific business checking listing') and explicitly contrasts its depth with the sibling's 'broad list results'. An agent can distinguish it from query_business_checking without opening either schema.

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?

Explicitly prescribes the workflow: 'Use this as a follow-up after query_business_checking to dig deeper on one listing the caller already identified by its listing_slug.' The alternative (broad list) and the condition selecting this tool are both named.

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