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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds one genuinely useful behavioral detail — bank_accounts come back with balances — but says nothing about pagination semantics beyond the schema, result size, or that catalogs are large reference sets. Adequate but thin on top of 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?

Two sentences, front-loaded with purpose, then the endpoint mapping. The endpoint list is partially redundant with the enum but is short and serves as a mental model for what each catalog contains. No wasted prose.

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 read-only paginated lookup with fully documented parameters and annotations, the description covers the essentials: which catalogs exist, why you'd fetch them, and that one catalog carries balances. Without an output schema, it could have sketched the returned fields per catalog, but nothing needed to call it correctly 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%, so the baseline is 3 and the schema already documents top/skip/filter/orderby in detail. The description earns one notch above baseline by explicitly enumerating the catalog values and mapping them to REST endpoints (/api/Locations, /api/Warehouses, ...), plus the branches/employees alias that the raw enum does not convey.

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 ('List one of the reference catalogs') and immediately scopes it to the set of lookup tables whose ids other tools need, which cleanly separates it from the sibling list tools that return clients, orders, invoices, etc. The parenthetical aliases ('locations (branches)', 'users (employees)') resolve name mismatches with the title.

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?

'whose ids other tools need' gives a clear reason to call this (resolving foreign-key ids before create/get calls), which is real usage context rather than a bare restatement. It does not state when not to call it or name a concrete alternative tool, so it falls short of a 5.

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