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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered; the description adds valuable behavior beyond that: pagination semantics with total as full count and truncated as a remaining-items flag. It also discloses a non-obvious side effect, that the call additionally returns the user's board sections. The field list compensates for the lack of an output schema.

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 what is returned and in what order, then paging, then the sections side effect, then routing to siblings. The long field enumeration is dense but each item earns its place given there is no output schema.

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 carries return-value burden well: it names every field, explains paging metadata, and covers the extra sections payload. An agent has everything needed to call it and to know which sibling to use with the resulting id.

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 both parameters are already documented, but the description reinforces the default of 20 and explains how limit/offset interact with total and truncated during paging. That is a modest but real addition over the schema's per-field text.

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 (Lists) and resource (the user's uploaded mortgage offers), clarifies the domain alias ("compositions"), gives the ordering (newest first), and enumerates the returned fields. It is clearly separable from get_mortgage (single item) and compare_mortgages among the siblings.

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 routes the agent downstream: use the returned id with get_mortgage / get_market_comparison / get_dashboard / ask_advisor, and notes that section ids are what update_mortgage accepts. It gives clear usage context but no explicit when-not-to-use condition or exclusion versus comparable listing tools.

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