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 only the requirement that clientId is mandatory; it says nothing about pagination behavior, result volume, or how the viewId filter narrows results, which would have been genuinely additive.

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 short, front-loaded sentences with zero filler; the required parameter constraint follows immediately after the purpose statement.

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 simple 5-parameter read-only list tool with no output schema and full schema coverage, the description covers purpose and the key constraint. It omits only nice-to-haves like pagination semantics and how results relate to connected reports, which the schema already partially handles.

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 100%, so every parameter (limit, viewId, clientId, nextToken, includeConnectedReport) is already documented with format hints like 'view_<hex> or hex'. The description's mention of clientId and viewId merely restates the schema, so 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 ('List') and resource ('account report themes'), which clearly distinguishes it from report_theme_get, report_theme_create, and report_theme_update. It stops short of explicitly naming the nearest sibling (report_theme_get for a single theme), so it lands at 4 rather than 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?

'List account report themes' implies the usage context, but there is no explicit when-to-use statement, no prerequisite guidance beyond the required clientId, and no named alternative for fetching a single theme. Usage is inferable but not articulated.

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