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 real behavioral context beyond that: the hiding suggestions are derived from an OnlyFans handle or an adult-work occupation on Wikidata and are non-binding, the hidden list is paginated 25 per page, and each hidden entry records whether a person or the sync (with the matched Wikidata claim) hid it. That is meaningful semantics an agent cannot get from 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 enormous sentence with parenthetical asides and dash-separated clauses. The resource is front-loaded, which is good, but the run-on structure makes it hard to parse and the density of detail ('an OnlyFans handle or an adult-work occupation on Wikidata') borders on over-specification for an agent deciding whether to call it.

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 read-only tool with an output schema already covering return values and a fully documented single parameter, the description supplies the domain framing needed to interpret the three result sections. The main gap is the lack of any routing to the mutation sibling, but the core calling information is present.

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% for the single 'page' parameter, so the baseline is 3. The description does mention '25 a page' and that page indexes the hidden list, which adds minor meaning beyond the schema, but not enough to lift it above the baseline.

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 — the homepage's Trending row — and enumerates the three things it reports: what is currently shown (and why), the entries suggested for hiding, and the entries already hidden. It is clearly a read/inspection tool and distinguishable in substance from write siblings like set_trending. However it never names the alternative, so differentiation is implicit rather than stated.

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 explicit statement of when to reach for this tool versus alternatives, nor any pointer to set_trending for actually changing the row. The presence of 'only a suggestion' and 'with the total waiting' implies a review/inspection context, but the agent must infer that this is the read counterpart to set_trending entirely on its own.

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