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

No annotations, so the description carries the burden. It discloses the return shape ('titles, summaries and links'), warns that full detail requires reading the article, and explains the semantics of an empty result set — useful behavioral context beyond the schema.

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?

Front-loaded with the core action, then structured into coverage, return value, and a practical tip. The long em-dash topic list is informative but slightly verbose; every clause still earns its place.

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 usefully explains what is returned and defers detail to the article itself. Combined with the empty-result guidance, an agent has enough to call the tool correctly, though limit/pagination behavior is unaddressed.

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 67%, so the schema documents most parameters. The description hints that queries should use the site's own vocabulary and references the 'site' section matching the category enum, but adds no syntax, limit behavior, or default details. Baseline 3 is appropriate.

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?

Specific verb+resource: 'Search RBX Invest's published guides.' The description scopes the corpus into market content and a named 'site' section, which cleanly separates it from sibling tools like search_items or get_started_guide.

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 clear context (searching published guides, browsing sections) and even advises re-querying with site vocabulary when a search returns nothing. It does not name a specific alternative sibling tool, so it falls short of a 5.

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