Search official Roblox documentation

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses a two-phase behavior: query returns matching pages and a path from those results is needed to read a page in full. This is useful operational context not available from the annotations alone.

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 description is three sentences with no filler. It front-loads the tool's purpose, then gives the workflow, then the use cases and sibling relationship. Every sentence 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?

The description covers purpose, workflow, use cases, and the key sibling alternative, which is enough for an agent to select and invoke it correctly. It does not detail return format or behavior of limit/max_tokens, but this is a minor gap given the otherwise strong guidance and rich schema defaults.

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 50%, and the description compensates for the key parameters by explaining that 'query' lists matching pages and 'path' reads the full page. However, 'limit' and 'max_tokens' receive no explanation beyond their default/min/max values, leaving some parameter semantics to inference.

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 states a specific verb ('Find and read') and a concrete resource ('Roblox's official creator documentation'), and explicitly contrasts it with search_devforum for production behavior. An agent can clearly distinguish this tool from its siblings.

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?

The description gives explicit when-to-use guidance ('intended behaviour, limits and quotas, and guide-level explanations') and names the alternative ('pair it with search_devforum for what actually happens in production'). It also provides the exact call sequence: query first, then path.

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