roblox_query

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description contributes real behavioral context by noting that count_only returns only a count in a single call and that results are paginated, but says nothing about error behavior, matching rules, or the shape of returned instances.

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?

Four terse sentences with zero filler, and the governing concept (exact search) is front-loaded. The clipped style borders on under-specification rather than pure conciseness, so it falls short of a 5.

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 10-parameter, no-output-schema search tool, the description is too thin. It never clarifies how name/tag/class filters combine, what 'exact' means versus the contains flag, or what a returned instance looks like, so an agent is left guessing on most of the call surface.

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 description coverage is only 10%, so the description must carry the load, and it only explains count_only. Parameters such as tag, name, class, root, contains, children_only, limit and offset receive no elaboration in either place, leaving most of the 10-parameter surface undocumented.

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?

States a specific operation (exact instance search) with a clear distinguishing qualifier ('exact'), so an agent knows it is a precise-match lookup rather than a fuzzy or tree traversal. It does not explicitly differentiate itself from siblings like roblox_get or roblox_advanced, which keeps it at a 4.

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 a search use case but gives no when-to-use condition or named alternative among the many siblings. The closest thing to guidance, 'No source/tree dump', hints at what other tools are for but never routes the agent explicitly.

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