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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description usefully frames the data as an audit log with incremental-sync semantics, but says nothing about ordering, pagination behavior beyond the schema's limit, or rate limits. With annotations carrying the read-only story, this is an adequate but not rich disclosure.

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 tight sentences front-load the core purpose and scope, followed by a short endpoint reference. Nothing is padded, though the raw 'Breeze: GET /api/account/list_log' line is marginally useful only for debugging.

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 six-parameter read tool with no output schema, the description covers purpose, filters, and rationale well, but omits anything about returned record shape or result ordering. An agent can invoke it correctly; it cannot predict what it will get back.

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 all six parameters are already documented with patterns, ranges, and the action enum. The description restates the date-range and user filters and gives a few action examples, but adds essentially no syntax or behavioral detail beyond the schema — the baseline 3 for schema-covered params.

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 names the resource precisely (the account's audit log), constrains it to one action type, and gives concrete enum examples (person_updated, tag_assign, contribution_added). It clearly reads as distinct from siblings like breeze_get_account_summary or breeze_list_contributions, which return state rather than a change history.

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?

It states the intended use cases explicitly: 'what changed since…' and incremental sync, which tells an agent when this tool is the right pick. It stops short of naming an alternative or a when-not-to-use condition, so it is clear but not exhaustive.

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