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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered; the description's 'compact read-only snapshot' is redundant with that. The genuinely additive behavioral disclosure is the entity_scope.ask_user interactive behavior when several entities are consolidated, but this arrives after a long enumeration of return fields that the output schema already covers, so the net new behavioral content is thin.

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 purpose and usage trigger are front-loaded in the first sentence, which is good, but the description then runs long enumerating return blocks (book_value, invoice_book, profit_and_revenue, data_coverage, etc.) that an output schema already documents. Much of that length does not earn its place and dilutes the key behavioral point about entity_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?

Because an output schema exists, the description need not re-explain return values, yet it spends most of its length doing so. The interactive entity_scope behavior is covered, but the description leaves the agent without routing guidance against the many overlapping dashboard-slice siblings, so completeness for correct invocation is only adequate.

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 the single entity_id parameter is already fully documented in the schema (including the consolidated-group default and aligned_blocks_scope_basis). The description adds no syntax, format or default detail beyond what the schema provides, so the 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+resource: 'Returns a compact read-only snapshot of the authenticated Hedgr dashboard,' and enumerates the scope (organisation, provider, base currency, entity context, exposure, P&L). It is clear what the tool does, though it never explicitly names the sibling slice tools (get_pnl_attribution, get_fx_exposure, get_cash_position) it aggregates over, so differentiation is left 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?

Provides one trigger condition, 'Use when the user asks for a dashboard-level summary,' which is more than nothing but gives no when-not guidance and names no alternatives, despite 26 heavily overlapping siblings. The agent must infer that this is the roll-up view versus the per-slice tools.

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