nexterm_list_scripts

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety behavior is covered. The description adds meaningful context with "accessible", indicating permission-based filtering, but says nothing about pagination, result ordering, or search matching behavior.

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 front-loaded sentence with no filler. It is perhaps overly terse given the missing sibling differentiation, but structurally it wastes nothing.

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 two-parameter list tool with no output schema and annotations covering safety, the description is minimally sufficient. However, it omits key context such as how it relates to nexterm_list_all_scripts and what the returned script list 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?

Schema description coverage is 0%, so the schema does not explain the two parameters. The description partially compensates by mentioning "search" and organization scoping, but it does not explain what fields the search parameter matches or whether organization_id filters to only that organization's scripts.

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 gives a specific verb and resource: "List or search accessible scripts". It distinguishes the operation from mutation siblings like nexterm_create_script and nexterm_delete_script, though it does not clarify how it differs from nexterm_list_all_scripts.

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 "optionally scoped to an organization" implies when the organization_id parameter is useful, but the description never states when to use this tool instead of nexterm_list_all_scripts or other script-list siblings. Usage is implied rather than explicitly guided.

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