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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds nothing beyond that — no indication of what data is aggregated, what filters are supported, result volume, or whether the dashboard is scoped to a workspace/period.

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 first sentence is duplicated verbatim, so half the text is pure waste. The remaining content (operation ID, describe_operation pointer) is terse but poorly front-loaded relative to what the agent needs first: what the tool does.

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?

No output schema exists, and the opaque open query object means the description carries the burden of explaining both inputs and returns — yet it explains neither. For a dashboard/aggregation endpoint with nested objects in the schema, an agent cannot determine what to pass or what to expect.

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 0% and the 'query' parameter is a fully open object with additionalProperties {}, so the schema conveys essentially nothing. The description only says describe_operation provides native request schemas, which is a useful pointer but does not tell the agent what query keys exist or their formats.

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 only repeats the raw HTTP path and operation ID, which is a tautological restatement of the title. An agent can infer the resource is a 'contract expense dashboard' under expenses, but nothing states what the endpoint actually returns or how it differs from concrete siblings like get_expenses_contract_period_overview or get_dashboard_expense_breakdown.

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 when-to-use guidance, no exclusions, and no comparison to the many similarly named expense/dashboard siblings. The only actionable routing information is the pointer to describe_operation for native request schemas, which helps with schema discovery but not with tool selection.

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