st.regex.registry

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

No annotations are provided, so the description carries the full burden. 'List' implies a read-only operation and 'global' scopes the resource, but it does not disclose output shape, side effects, or metadata semantics. It adds some context but remains minimal.

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?

A single sentence with no filler, front-loaded with the action and resource. It is appropriately concise, though the phrase 'normalized placement metadata' is dense and could be clearer.

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 zero-parameter listing tool, this is almost enough: the resource and scope are clear. However, with no output schema, the description does not clarify what 'normalized placement metadata' contains or what shape the returned list takes, leaving a meaningful gap.

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 haseeen 0 parameters and the schema is trivially covered. Description does not describe parameters because none exist, which is acceptable. Baseline of 4 applies for zero-parameter tools.

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 ('List') and a specific resource ('global ST regex scripts'), and mentions the output ('normalized placement metadata'). It is clear enough to distinguish from siblings like st.regex.configure, though it does not explicitly name an alternative.

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?

it does not provide guidance about when to use this tool versus alternatives, nor does it mention exclusions or prerequisites. The intended use is implied by 'List' but no explicit usage context is given.

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