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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, and the description adds essentially nothing on top — only that the ChannelOAuthId header is "resolved internally" and that output "returns the result or applies the effect," which is vacuous for a read tool.

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?

Boilerplate dominates: "explicit tool with a fixed endpoint," "functional documentation," and a redundant "Search terms" line that repeats the tool name twice. The actual informative content could fit in one sentence, and the purpose is buried rather than front-loaded.

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?

An output schema exists, so return values need no explanation, but the description still never tells the agent what entity or metric this endpoint returns or under what dashboard context to call it. For a one-parameter read tool that is technically callable, it leaves the semantic decision — which dashboard endpoint to pick — unsupported.

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 coverage is 100% and the single parameter's description already explains it is the ChannelOAuthId from hgr_list_channels. The description only echoes that a channel header is required, so 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?

The description restates the tool name and endpoint ("GET api/Dashboard/TaskPendingAutoOrder2") but never explains what "task pending auto order2" data actually is. Its only distinguishing claim — that it is "not a generic endpoint caller" — differentiates it from a hypothetical generic tool, not from any of the many dashboard siblings it is listed beside.

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 guidance is circular: "Use it when a client needs to run the task pending auto order2 operation for dashboard data." No when-not conditions, no alternatives among the dashboard siblings (e.g. getpendingstatistics, getoptimizedcount), and no prerequisites beyond a header reference.

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