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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds one genuine behavioral fact not in the annotations: results are ordered newest first. It says nothing about default page size, max limit, or empty-result behavior beyond what the schema states.

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?

A single front-loaded sentence with no filler; the sort order and pagination/filter capabilities are stated up front. It is perhaps too terse for an 8-parameter tool, but nothing is wasted.

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 filtered, paginated list over 8 parameters with no output schema, the description covers the essentials (group scoping, ordering, pagination, filtering) but leaves defaults, max limits, and return shape unstated. Adequate as a minimum-viable definition, not more.

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 63% and several parameters (type, currency, groupId) carry no schema description at all, yet the description only offers the generic phrase 'filters'. It adds no meaning to any specific parameter, so it fails to compensate for the coverage gap.

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?

Names a specific verb and resource ('List transactions of a group') and adds the sort order ('newest first'), which separates it from list_personal_transactions and get_transaction. It does not explicitly call out its siblings, so it falls short of a 5.

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?

There is no when-to-use guidance, no prerequisites (e.g. must be a group member), and no pointer to list_personal_transactions or get_transaction for other scopes. 'with pagination and filters' describes capability, not selection criteria.

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