startup_script_list_startup_scripts

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only states the action without explaining scope, filtering, ordering, or pagination behavior. It conveys a read-only property but adds no detail about what 'all' encompasses or potential limitations.

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 first sentence is concise and front-loaded, but the 'Returns: List of startup scripts' line merely restates the resource and adds little value. It is a complete but not fully efficient usage of sentences.

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?

An output schema exists and this is a simple no-parameter list operation, so the description is mostly sufficient. However, it omits any explanation of how this listing differs from the two other startup_script list variants (boot, PXE) and the search tool, which can lead an agent to select the wrong sibling.

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 tool has zero parameters and the schema coverage is 100%, so there is nothing for the description to add. Baseline 4 applies: with no parameters, the description cannot be expected to provide parameter-level semantics.

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 a clear verb and resource: 'List all startup scripts.' This distinguishes it from the generic 'get' and 'search' siblings, but it does not explicitly differentiate it from startup_script_list_boot_scripts or startup_script_list_pxe_scripts, so it falls short of full sibling differentiation.

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 description provides no guidance on when to use this tool versus alternatives like startup_script_search_startup_scripts, list_boot_scripts, or list_pxe_scripts. An agent cannot determine whether 'all startup scripts' means all types or why it should choose this over the search variant.

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