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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered structurally. The description adds nothing beyond that — no note on auth/scope requirements, cost of the call, caching, or what data the endpoint aggregates. It does not contradict annotations, but it is purely a path echo.

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 same path sentence appears verbatim twice, which is pure waste, and the operation ID hash adds no decision value. The one useful pointer (describe_operation) is buried at the end of a run-on clause.

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?

With no output schema, 0% param coverage, and a nested free-form 'query' object, the description would need to explain the return shape or the meaningful query keys. It only redirects to describe_operation, which is a partial mitigation but not enough for an agent to invoke this correctly without an extra tool call.

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?

Both parameters (query and params) have 0% schema description coverage, and 'params' has no declared properties at all. The description must compensate and instead says only that native schemas live in describe_operation, leaving an agent with no idea what query keys or filters are accepted.

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 repeats the HTTP path 'GET /api/dashboard/metrics' twice, which is essentially a restatement of the tool name/title rather than a statement of what the metrics represent. It never says what is measured, over what scope, or how it differs from the many sibling dashboard tools (expense breakdown, status breakdown, recent activity, widgets).

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 only actionable guidance is that 'describe_operation provides native request schemas', which is a pointer for schema discovery rather than a when-to-use rule. There is no mention of when this aggregate metrics endpoint should be preferred over get_dashboard_status_breakdown or get_dashboard_expense_breakdown, and no prerequisites or exclusions.

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