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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so safety is covered. The description adds nothing beyond that — no mention of what the stats measure, the aggregation window, or scoping requirements. It only references describe_operation, which is a discovery hint rather than behavioral context.

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 sentence is duplicated verbatim, wasting half of an already very short description. Nothing is front-loaded beyond the path restatement.

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% parameter documentation, and a generic nested-object schema, the description is the only place meaning could come from — and it provides none. An agent cannot determine what this returns or how to scope the request from this definition alone.

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 both parameters are opaque generic containers ('query' with arbitrary properties, empty 'params'). The description supplies no parameter meaning at all, leaving the agent with no idea what can be filtered or passed.

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 body merely repeats the raw path 'GET /api/redline-tasks/stats' twice, which restates the title and name rather than describing in plain language what the stats represent. An agent learns only that it is a read of some aggregate for redline tasks, with no distinction from siblings like get_redline_tasks_dashboard or get_redline_tasks_stats-adjacent analytics endpoints.

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 guidance is 'describe_operation provides native request schemas', which is a schema-discovery pointer, not a when-to-use rule. There is no statement of when to prefer this stats endpoint over get_redline_tasks, get_redline_tasks_dashboard, or the get_redline_analytics_* family.

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