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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so the safety profile is covered. Beyond that the description only says it "returns the result or applies the effect," which is generic filler, and the claim that channelOAuthId is "resolved internally" is at odds with the required-parameter schema, potentially misleading an agent about auth. No disclosure of what data is returned, freshness, or cost.

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: the "explicit tool with a fixed endpoint; it is not a generic endpoint caller" sentence conveys little, and the auth note is repeated at both the start and the end. The single genuinely useful clause (search terms) is buried after redundant scaffolding.

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 not be described, but the description still fails to say what the count represents, what unit it is in, or when it beats the many neighboring dashboard endpoints. For a one-parameter read in a dense sibling set, this leaves the agent unable to choose it confidently.

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% and the single parameter's schema text ("returned by hgr_list_channels for the selected visible store") is strictly more informative than the description's "Header channel: current ChannelOAuthId." Baseline 3 applies since the schema does the work.

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: "Provides the GET get optimized count operation in dashboard data." It identifies the HTTP verb and endpoint but never explains what an "optimized count" actually counts, which is the one thing an agent cannot infer from the name. Sibling tools like hgr_get_dashboard_getlistingsummary or hgr_get_dashboard_getpendingstatistics similarly get no differentiation.

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?

"Use when: Use it when a client needs to run the get optimized count operation for dashboard data" is circular – it tells the agent to use the tool when it needs the tool. No exclusions, prerequisites, or comparison to the other 15+ hgr_get_dashboard_* siblings are offered. The only concrete guidance is the passive note that channelOAuthId comes from hgr_list_channels, which duplicates the schema.

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