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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. However, the description adds essentially no behavioral context beyond the raw data categories returned; it does not mention pagination, defaults, filtering behavior, or access constraints.

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 a compact single sentence with no filler words Opportunities to clarify parameter semantics were missed, but what is present is efficient and front-loaded with the core subject.

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 available output schema and annotations cover return structure and read-only safety, so not all gaps are critical. But the description leaves the three optional parameters unexplained and offers no usage context, so an agent cannot confidently decide how to filter or paginate.

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 0%, and the description does not explain limit, status, or household_id. The default values (100, ACTIVE, empty string) are visible in the schema but their meaning and effect are entirely undocumented. With low coverage spread across three parameters, the description needed to compensate and did not.

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 identifies the resource ('Credit facilities') and lists the data fields returned (balances, limits, rates, maturities, covenants, collateral), so an agent understands what this list returns. It does not explicitly distinguish itself from the sibling get_facility, but the plural 'facilities' and list of attributes convey the list nature clearly.

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 alternatives such as get_facility or list_accounts. There is no mention of filtering, prerequisites, or when this tool is appropriate, leaving the agent to infer usage from the name alone.

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