list_parser_presets

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

With no annotations, the description bears full responsibility. It conveys that the tool reads and returns stored presets, implying a non-destructive operation, but does not explicitly state read-only behavior, pagination, or ordering. Since this is a simple list, the omission is minor but leaves some behavior to inference.

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, concise sentence that front-loads the action and resource, then enriches with the key attributes. No fluff or repetition; every word 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?

For a parameterless list operation, the description is fairly complete, covering the resource and the nature of the output. It lacks explicit mention of return format (e.g., array) or pagination, but given the simplicity and absence of an output schema, it is sufficient for an agent to understand and invoke correctly.

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, so the baseline is 4. The description adds value by detailing what information is included in the listing (version, health stats, changelog), exceeding the empty schema. This provides meaningful context for the agent about expected output.

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 states the verb 'List' and the resource 'your stored parser presets', and further specifies the included attributes (version, health stats, changelog). This effectively differentiates it from sibling tools like generate_parser or parser_preset_stats without ambiguity.

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?

While the description does not explicitly name alternative tools or conditions for non-use, the purpose is self-evident for a simple list operation, and the resource target is unambiguous. It clearly implies use when you need to view existing presets, which is adequate for this straightforward tool.

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