script_template_search

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

With no annotations, the description carries the full burden. It only says 'Returns events' but does not disclose whether the operation is read-only, idempotent, or has side effects. No mention of authentication, rate limits, or pagination behavior, though 'from' and 'size' hint at pagination.

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 very short (one sentence), but it is cryptic and lacks clarity. Conciseness is achieved at the expense of comprehensibility.

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?

Given 7 parameters, no output schema, and no annotations, the description is far from complete. It fails to explain what script templates are, how the search works, or what the response contains.

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 schema has 100% coverage, so the baseline is 3, but the description states 'Required: q, from, size' while the schema shows all parameters as optional (default null). This contradiction reduces the score. The description adds no new meaning beyond the schema's param descriptions.

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 the HTTP method and endpoint (POST /scriptTemplate/search) and says 'Returns events', giving a basic sense of the tool's action. However, it does not clearly define what script templates are or what kind of events are returned, and it does not differentiate from sibling search tools like 'script_template_commands_search_by_fields'.

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?

No usage guidance is provided. The description does not indicate when to use this tool versus other search tools among the siblings, nor does it mention prerequisites or when not to use it.

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