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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the period breakdown and the 'mini/dashboard' nature, implying a compact high-level view, but it does not disclose behaviors like data freshness, timezone handling, or how currency affects the cards.

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 a single, tightly packed phrase that front-loads the core concept ('dashboard mini-P&L cards') and lists the periods in parentheses. There is no filler or redundancy.

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 tool with no output schema and two optional parameters, the description says what periods are covered but omits what each card actually contains (e.g., revenue, profit, margin), how currency or seller_connection_id filter the data, and when to select this over other P&L tools. The large sibling set amplifies this gap.

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 only 50% (currency has no schema description). The tool description does not explain either parameter or how they influence the results, failing to compensate for the undocumented currency parameter. Only seller_connection_id has schema-level documentation.

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 identifies a specific resource, the dashboard mini-P&L cards, and enumerates the exact periods covered (Today / Yesterday / MTD / This-month forecast / Last month), which helps distinguish it from P&L tools like pnl_summary or pnl_breakdown. However, it lacks an explicit verb such as 'returns' or 'displays,' making the action slightly implicit.

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 guidance on when to use this tool versus the many sibling P&L tools. The description does not mention alternatives, exclusions, or decision conditions such as 'use this for the dashboard cards' or 'use pnl_breakdown for detailed analysis.'

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