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

Annotations already establish read-only, idempotent, closed-world behavior, and the description layers on material traits the annotations cannot convey: a trial quota of 3 calls per source per day, a freshness limit (latest day only), and an explicit prompt-injection warning that song titles, artist names and quotes are data rather than instructions. That is substantial behavioral disclosure.

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 front-loaded with what the chart is, then moves through field semantics, the freshness limit, a safety note, and the quota. Every sentence carries information, though the single dense paragraph could be split for scanability.

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, the description carries the burden of explaining return values, which it does (as_of = chart date, score = spark value, count = chart appearances, explicitly not play counts). Combined with freshness limits, quota and injection warnings, an agent has everything needed to call and interpret it.

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?

The tool takes zero input parameters, so the baseline is 4. The description's explanation of as_of, score and count describes output fields rather than inputs, which is useful but does not change the fact that there are no parameters to document.

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 names a specific resource and its exact scope: today's public chart of hot songs and hot quotes, top 20 each, identical for all viewers. An agent can tell immediately what this returns without consulting the schema, and the sibling tools (about_meowspace, apply_for_access) are unrelated enough that no differentiation is needed.

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?

It gives a clear usage constraint — only the latest day is available and history cannot be paged — plus a fallback path: after the 3-per-day trial quota is exhausted, guide the user to apply for access (the apply_for_access sibling). It does not explicitly state when to prefer this over any other data source, but no competing tool exists, so the gap is minor.

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