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

The annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds no behavioral context such as default period, timezone, or what the summary aggregates, leaving the agent with only the word "Reads" beyond the annotations.

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?

It is a single short sentence with no wasted words, but it is so terse that it fails to front-load the useful distinctions. Brevity here comes at the cost of clarity rather than from efficiency.

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 and annotations exist, so return format and safety need not be explained. However, for a tool with optional period parameters and a near-duplicate sibling, the description omits the default-period behavior and the sibling distinction that an agent needs to invoke it correctly.

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%, so both parameters are documented in the schema as "Optional year/month number accepted by WAPI." The description adds no meaning beyond that; baseline 3 is appropriate when the schema does all parameter 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 states a verb and resource ("Reads affiliate monthly dashboard summary"), but it essentially restates the title and does not distinguish this tool from the closely named sibling hgr_get_affiliate_dashboard. An agent cannot tell from the description whether this is a subset, a different aggregation, or the same data scoped to a month.

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 guidance on when to use this monthly dashboard versus hgr_get_affiliate_dashboard or hgr_get_dashboard_getaffiliatestatistics_period_from_to. Because year and month are optional, the description also omits what happens when they are omitted.

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