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

With no annotations, the description carries the full burden and it does disclose useful traits: each result carries a citable url, the data-use entry returns licensing terms in full, and the tool summarizes badge catalog, socials, and sponsorship content. It is silent on match semantics (substring vs natural-language), result caps, and whether the omitted query returns a paginated dump, which matters for a list-returning tool.

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?

The purpose and query mechanics are front-loaded, which is good, but the middle is two dense enumerations of content categories that partially repeat each other and crowd out the routing information that would actually help. Several clauses could be consolidated without losing meaning.

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 must describe the return shape, and it does: a result set of pages each with a url, plus full licensing text for the data-use entry. For a single-optional-param lookup tool this is nearly sufficient; only result counts and matching behavior are left unstated.

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 100% so the baseline is 3, and the description adds real value beyond the schema: concrete example queries ('market data', 'dominus', 'can I reuse your data') that show the query behaves as natural-language intent matching rather than exact title matching. It also reinforces the omit-for-everything behavior already in the schema.

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 clearly states a specific verb+resource: locate any page on rbxinvest.com by keyword, returning its url. It enumerates the page categories (market pages, guide levels, article sections, collections, support, licensing, developer docs), which makes the scope concrete, but it never distinguishes itself from overlapping siblings like find_articles, get_collection, or get_started_guide, whose content it explicitly claims to cover.

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 usage pattern ('Pass a few words of what you are looking for'; 'omit the query for the full list') and names additional question types it serves, but offers no when-not guidance and no routing against the siblings that cover the same content. The agent must infer whether to call this or find_articles for article content.

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