script_list

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

With no annotations, the description carries full burden but only states 'List and discover available scripts' without disclosing read-only nature, output format, pagination, or any side effects. It adds no behavioral context beyond the name.

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 and front-loaded, but 'List and discover' is mildly redundant. It is a single sentence with no unnecessary detail, yet it omits useful information that could be included without bloat.

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 the absence of an output schema and annotations, the description should at least mention what the returned list contains or how it complements script_get. It lacks any indication of return value structure, workspace scope, or usage flow, making it incomplete.

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?

Both 'tag' and 'search' parameters are fully documented in the input schema with descriptions, so the baseline is 3. The description adds no additional semantic detail about how filters interact with the list.

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 clearly identifies the tool's function as listing/discovering scripts, using specific verbs 'list' and 'discover' on the 'scripts' resource. It differentiates from siblings like script_add/rm/run by operation type, though it does not explicitly reference alternatives, so it falls short of a 5.

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 guidance is provided on when to use this tool versus script_get or whether to combine with tag/search filters. The description lacks any contextual cues or exclusions, leaving the agent to infer usage.

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