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

Annotations already cover readOnly/destructive/openWorld, yet the description still adds real behavioral detail: required scope, fixed page size of 50, newest-first order, and what each row contains including the human-delivery reason.

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?

Four short sentences, front-loaded with what is listed and in what order, then safety/scope, then row shape and the empty-result interpretation. No filler.

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 usefully explains the returned rows, the delivery-reason field, and what an empty list means. Only minor gaps remain, such as the hasMore/pagination interaction, which the schema covers.

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 documents offset semantics and the app_/usr_ key default better than the description does. The description only contributes the 50-per-page fact that makes the offset hint usable, so the baseline 3 applies.

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 Tribute payments), scopes it to the application, and adds ordering plus page size ('newest first, 50 per call'), which immediately separates it from the sibling products tool.

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?

Gives the required scope (read_payments) and clarifies the empty-list case, which is genuine usage context, but it never names an alternative or says when another tool (e.g. list_tribute_account_products or retry_tribute_delivery) is the better pick.

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