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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, and the description still adds real context: an account token is required, the call does not charge, and the no-parameter case degrades to a listings response rather than an error. No return-format or pagination detail is given, keeping it at 4.

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?

Four tight sentences, front-loaded with the auth requirement, then the return content, then parameter roles, then the fallback and cost note. Each sentence carries information an agent needs; nothing is redundant.

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 and only two optional parameters, the description covers the return payload (embed line/ribbon contents), the auth prerequisite, the fallback behavior when no parameters are passed, and the non-billing guarantee. Nothing needed to invoke it correctly is missing.

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%, so the baseline is 3, but the description adds semantic meaning the schema does not: 'site' must be a site on this account, 'host' must be a confirmed winner, and both are optional with a defined fallback. That exceeds what the schema alone conveys.

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?

States a specific verb and resource: returns the embed line for a Site of the Month award, and describes what the returned ribbon contains (award name, period, verification link). It never explicitly distinguishes itself from siblings such as award_readiness, so it lands at 4 rather than 5.

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?

Gives concrete selection logic: 'site' targets a site on this account, 'host' targets a confirmed winner, and with neither the tool lists the account's earned awards. That is clear when-to-use context, though no alternative tool is named for these cases.

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