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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds nothing further: it does not say whether this returns a full document, links, or a structured config, nor anything about size, caching, or auth. The topic enumeration is the only added substance, and it is thin.

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?

A single short fragment with no waste, appropriately sized for a no-argument tool. It is not front-loaded with a verb or outcome, so it reads as a label rather than a lede, which keeps it just below top marks.

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?

For a simple read-only, no-parameter tool with annotations covering safety, the description is adequate but leaves the agent unsure whether it gets prose documentation, a settings object, or contact links. No output schema exists, so a little more on the shape of the response would have closed the gap.

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?

With zero parameters there is nothing to disambiguate, so the baseline of 4 applies. The description's topic list does at least scope what kind of information the parameterless call yields.

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 enumerates the subject matter the tool covers (payments, tracking, compliance rules, contact), which tells the agent what information it surfaces, but it never states a verb or resource explicitly — 'How RottenAds works' is a topic label, not a purpose statement. Siblings like get_offer, list_verticals and search_offers are clearly different, so confusion risk is low, but the tool itself is only vaguely characterized as an unspecified overview/help resource.

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 indication of when an agent should call this versus the other tools, no prerequisites, and no exclusions. The topic list implies it is a general reference/help endpoint, but the agent must infer that itself.

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