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

Annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds useful behavioral context beyond them: the list is proactive and ranked, each item includes a plain-English reason and a location to fix it, and the agent should proactively offer help with the most important items.

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?

The description is front-loaded with purpose and scope, then follows with usage guidance and output expectations. It is somewhat long but the enumerated categories earn their place by defining the aggregation scope.

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?

There is no output schema, so the description carries the burden of explaining what comes back. It does so adequately by listing item categories and saying each item includes a reason and a fix location, though it does not describe the exact result shape or empty-state behavior.

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%, and the single optional 'company' parameter is fully documented there. The description does not add parameter-level detail beyond the schema, so the baseline 3 is appropriate.

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 states a specific verb and resource: return a proactive, ranked attention list across the whole account. It enumerates the categories included (missing statements, unreconciled transactions, deadlines, close tasks, overdue invoices, open tasks), making it clearly distinct from sibling tools that each cover only one domain.

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 gives strong when-to-use guidance with concrete user phrasings such as 'what do I need to do', 'what's outstanding', 'status check', and 'what should I focus on'. It stops short of naming explicit alternatives or when-not-to-use conditions, so it is clear but not fully exhaustive.

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