List fabricators

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description usefully adds where the list comes from ($AIKEA_HOME/fabricators.json or the AIKEA_FABRICATOR_WEBHOOK env var), which helps an agent reason about configuration state, but it says nothing about what happens when neither source exists (empty list vs error).

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 front-loaded sentence with the core action first and configuration sources relegated to a parenthetical. Nothing is wasted, though the file-path/env-var detail is closer to implementation trivia than selection-relevant information.

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 read-only list tool with readOnlyHint covering safety and no output schema required, the description covers the essential purpose and data source. The only gap is whether the result is an empty list or an error when no fabricators are configured.

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 takes zero parameters and the schema is trivially complete, so the baseline of 4 applies. There are no parameter semantics for the description to clarify or omit.

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 names a specific verb ('List') and resource ('CNC shops configured for quotes'), which is clearer than the bare title 'List fabricators' and tells the agent this returns quote-capable shops rather than, say, designs or options. It does not explicitly differentiate itself from siblings like aikea_list_options or aikea_list_designs, but the resource is distinct enough to disambiguate.

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?

There is no statement of when to call this versus alternatives, nor any prerequisite or ordering guidance (e.g., call before aikea_request_quote or aikea_add_fabricator). Usage is only implied by the verb 'List'.

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