list_parameters

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

Describes return value comprehensively (JSON with schema details), implying idempotent read operation. No annotations provided, but description adequately conveys behavior for a simple data retrieval tool.

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?

Three succinct sentences: one for purpose, one for output detail, one for usage advice. No redundant information, well structured.

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 presence of output schema, description covers essential input constraints (none) and output contents. Includes proactive usage guidance, making it fully sufficient for an agent to 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?

No parameters, and description adds value by detailing the output content beyond the empty input schema, compensating fully for zero parameters.

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?

Explicitly states it returns the full documented Serum 2 parameter schema as JSON, specifying contents (modules, ranges, units, enums, verification confidence). Distinguishes from siblings (generate, edit, describe presets) by focusing on schema retrieval.

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?

Directly advises to call before proposing an edit to know valid parameter names and ranges. Provides clear context for use, though does not explicitly list when not to use or alternatives beyond sibling tools.

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