script_class_list

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does add useful behavioral detail by stating the filter is case-insensitive and optional, but it does not describe the return format, sorting, or any limitations. For a simple listing tool this is acceptable but not rich.

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 two short lines with no filler. The core purpose is front-loaded and the parameter documentation is directly attached. Every sentence earns its place.

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?

This is a low-complexity listing tool with a single optional parameter, and the description covers both purpose and parameter semantics. The only notable gaps are the lack of explicit return-shape details and lack of alternatives, but for this simple tool the description is largely sufficient.

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 only defines pattern as a nullable string, while the description adds meaningful semantics: 'Case-insensitive substring.' This goes beyond the schema by explaining how the parameter is interpreted. It does not cover edge cases like empty-string behavior, but the main semantic is present.

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 uses a specific verb and resource: 'List names in the td module.' It clearly states the tool lists names and supports an optional substring filter. However, it does not explicitly distinguish itself from the sibling script_class_detail, so the differentiation is only implied by the name and context.

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 offers no explicit guidance on when to use this tool versus alternatives such as script_class_detail or script_module_help. It describes the pattern parameter but does not state a selection criterion or mention sibling tools, leaving usage context to inference.

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