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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, covering safety. The description adds valuable behavioral context: it returns a 'verified' PNG with 'integrity receipts,' implying data integrity verification, and it imposes a data accuracy contract (only treat returned fields as verified, no invented/inferred metrics). This exceeds the minimal annotation coverage without contradicting it.

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 structured into three clear segments: purpose, inputs, and usage instructions (including the required suffix and data accuracy contract). While it is longer than typical descriptions, every sentence contributes meaningful requirements; the front-loaded purpose is immediately clear. The length is justified by the complexity of the data integrity rules.

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?

Given the presence of an output schema (not shown here but noted in context signals), the description adequately explains the return format (verified PNG dashboard with accessible text and integrity receipts) and sets expectations for data handling. It covers inputs, output characteristics, and post-processing rules, leaving no critical missing information for correct invocation and result interpretation.

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 schema already documents both start_date and end_date with patterns, defaults, and descriptions. The description merely repeats that inputs are optional, adding nothing beyond the schema. This meets the baseline of 3 for high schema coverage, with no additional semantic value added.

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 explicitly states the tool retrieves specific QuickBooks financial reports (Profit and Loss, Balance Sheet, AR/AP aging, company reports) and returns a verified PNG dashboard with reconciled facts, accessible text, and integrity receipts. This is a precise verb-resource pair that clearly distinguishes it from other dashboard tools in the sibling list, all of which are platform-specific (e.g., ahrefs_dashboard, stripe_dashboard).

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?

The description provides clear operational guidance (inputs, required response ending, data accuracy contract) but does not explicitly state when to use this tool versus the corresponding quickbooks_connector or other report tools. The context implies it is for QuickBooks dashboard needs, but no exclusions or alternatives are mentioned, leaving the decision to inference.

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