Query Roblox instances

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

Annotations already declare readOnlyHint and idempotentHint. The description adds the behavior of being 'bounded' and 'fast,' but does not detail limits like maxResults or scan bounds. It offers minimal extra beyond annotations.

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?

Single sentence, front-loaded with 'Fast bounded instance search.' No redundancy; all terms are meaningful.

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 12 parameters and no output schema, the description is too sparse. It doesn't explain the return value, how results are ordered, or what 'bounded' means in practice. The tool's complexity demands more context.

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 only 8%, so the description must compensate. It maps to several parameters (className, nameContains, tag, attribute, maxDepth, withinStuds) but omits properties, maxResults, maxScanned, and clientId. It provides intuitive labels but not detailed semantics.

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 'Fast bounded instance search' with explicit filter dimensions (root, class, name substring, tags, attributes, depth, distance from player), clearly distinguishing it from sibling tools like get_tree or inspect_instance.

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 implies the tool is for filtering instances by criteria but does not mention when to prefer it over alternatives like get_tree or wait_for_instance. No exclusions or alternatives are named.

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