Search script collections

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

Annotations already declare readOnlyHint=true, and the description does not contradict that. The description adds some behavior context by clarifying the lookup is direct/entity-based, but it does not disclose other behaviors such as result limits, error conditions, or the role of the optional name parameter.

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 a single sentence, front-loaded with the action and resource, and contains no filler. The parenthetical 'direct entity lookup' adds meaningful clarification without bloating the definition.

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 simple read-only lookup, the description is close to adequate, especially with the readOnlyHint annotation. However, the silent treatment of the name parameter and the lack of explicit differentiation from get_script_collections leave meaningful gaps for an agent deciding between tools.

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 0%, so the description must compensate. It names id and version but omits name, and it does not explain whether parameters are combinable, optional, or required in any particular way. This leaves the agent guessing about how to construct a valid lookup.

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?

Description states a clear action ('Search script collections') and a specific scope ('by ID and version (direct entity lookup)'). It conveys that this is an exact lookup rather than a broad search, though it does not explicitly differentiate itself from get_script_collections.

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 phrase 'direct entity lookup' implies this is appropriate when the caller already knows the ID and/or version. However, it does not explicitly say when not to use this tool, nor does it name alternatives like get_script_collections or other search tools.

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