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

Beyond readOnlyHint=true, it discloses what actually comes back ("Returns links only; the pages are the source"), that no underlying data request is triggered, and that the call spends nothing — cost and output-shape context an agent cannot infer from annotations. It also documents an information boundary, warning that pillar-combination logic is deliberately absent from the corpus.

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?

Three tight sentences, front-loaded with the primary action and parenthetical topic inventory, then progressively narrower qualifiers. No filler and nothing repeated from the schema or annotations.

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 a single optional parameter, no output schema, and only a readOnlyHint annotation, this description covers the remaining gaps: it explains the return type (links only), the call's cost profile, and a key limitation. Nothing an agent needs to invoke or interpret the result 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 already 100%, so the baseline is 3. The description adds real value on top by enumerating the valid topic families and giving an example key ('core_economic_profit') alongside the omit-to-list-all behavior, which clarifies the semantics of an optional, unenumerated string parameter.

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 opens with a specific verb and resource ("List Returnolio's published methodology pages") and then enumerates the exact topic set (score, quality, core economic profit, margin of safety, fair value, momentum, smart money, Top 10 selection), which distinguishes it from siblings like get_core_economic_profit or get_top10 that return actual data for those same topics.

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 states both modes of use clearly: omit the argument to list all pages, or supply a topic to fetch one. It also sets a negative expectation ("How the pillars combine into the headline score is not published"), which prevents wasted calls. It does not name a sibling alternative, so it falls short of the explicit when-not/alternative routing of a 5.

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