script_template_commands_search_by_fields

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

No annotations provided. Description does not disclose whether the tool is read-only, destructive, or any side effects. No mention of authentication, rate limits, or pagination. The phrase 'Get object by connection' is vague.

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?

Very short but wastes characters on the HTTP method and endpoint instead of clarifying purpose. Lacks front-loaded key information; the first part is essentially a repeat of the tool name.

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 no annotations, no output schema, and 9 parameters, the description is severely incomplete. It fails to explain what the tool returns, how 'connection' is used, or any usage scenario. The description is insufficient for correct tool selection and invocation.

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 description need not re-explain parameters, but it incorrectly states that three parameters are required, contradicting the schema. It adds no meaningful interpretation beyond parameter names.

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 'Get object by connection' and lists parameters, but does not clearly explain what 'connection' refers to or what the tool does beyond a search. It fails to distinguish from sibling tools like 'script_template_search' or 'automation_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?

Claims 'Required: from, size, q.' but the input schema shows no required properties, creating a contradiction. No guidance on when to use this tool versus alternatives, nor any context about prerequisites or limitations.

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