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

No annotations are provided, so the description carries full burden for behavioral disclosure. While it mentions semantic and lexical matching, it fails to disclose significant side effects: requireFullIndex defaults to true and may build/refresh the semantic index, and indexOnly can trigger a build without searching. These are important behavioral traits an agent should know before calling.

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?

Two compact sentences with no filler. The core purpose is front-loaded and the usage guidance is delivered in the second sentence, making it easy to scan.

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 and schema together cover purpose, parameters, and routing, but the lack of an output schema and no description of return format leaves a gap. More importantly, the default behavior of building the index is not surfaced in the description, which could lead to unexpected expensive operations.

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. The description adds meaning beyond the schema by clarifying that the query can contain exact lexical signals (identifiers, strings) in addition to natural language, which directly informs how to use the query parameter.

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 uses a specific verb ('Find') and resource ('decompiled Roblox scripts'), and clearly states the method ('by behavior using enriched semantic cards plus exact lexical signals'). It also differentiates from the sibling tool script-grep, making the tool's purpose unambiguous.

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?

Explicitly states when to use this tool ('when exact identifiers are unknown') and names the alternative ('use script-grep for precise text or regex'). This gives the agent a clear decision rule with no inference required.

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