list_presets

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

The description discloses that presets generate multiple interconnected resources with database models, CRUD endpoints, and Swagger docs. It also states that all presets auto-install JWT authentication and wire resources together. Since no annotations are provided, this description fully covers behavioral aspects such as side effects and capabilities.

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 concise with three sentences. The first sentence states the core action, the second provides detailed output description, and the third gives usage instructions. Every sentence adds value, and there is no wasted verbosity.

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 simplicity of the tool (no parameters, no output schema), the description is complete. It explains what the tool returns (list of presets with their generated resources), its role in the workflow, and its integration with init_project. No gaps remain.

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 no parameters, so the input schema provides no information. The description implicitly confirms that no inputs are needed by stating 'Call this first' without any input requirements. This is sufficient and adds no confusion.

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 starts with 'List all available domain presets', which is a specific verb and resource. It clearly distinguishes its role from sibling tools like init_project by explaining that it provides presets for the user to choose before calling init_project.

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 explicitly states when to use this tool: 'Call this first to help the user choose the right domain'. It also provides a clear follow-up action: 'then call init_project with --preset to generate it'. This gives direct guidance on usage context.

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