Search Roblox bug reports

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

Annotations declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, and the description adds meaningful behavioral details beyond that: search results include category, last-activity date, and solution-marked status, but there is no public triage state. It also tells the agent to read the thread via get_thread to verify staff response, which is valuable operational context.

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 sentences with no filler. Scope and intended use are front-loaded, followed by a useful caveat and a concrete next-step instruction. Every sentence contributes to helping the agent decide and invoke the tool correctly.

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 search tool without an output schema, the description adequately covers what is searched, what a hit contains, and how to get deeper detail. The limitation about triage state is important and addressed. No critical operational information 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?

The input schema already documents query, area, and after in detail, covering the main parameters. The description itself adds no parameter-level meaning and does not clarify limit or max_tokens, though those are inferable from names and defaults. Schema coverage is 60%, so the description provides modest overall value but leaves the minor parameters 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 and resource: 'Search only the DevForum bug-report categories,' explicitly enumerating the categories. It also ties the tool to a concrete use case, distinguishing it from generic DevForum search by framing it as answering 'is this a known Roblox bug or is it my code?'

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 clearly tells the agent when to use this tool: to check whether a symptom is a known Roblox bug. It also warns about a limitation ('Roblox does not tag reports with a public triage state') and directs to get_thread for follow-up. However, it does not explicitly name search_devforum as the alternative for non-bug-category searches.

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