list_local_grids

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

With no annotations, the description carries the full transparency burden and does so thoroughly. It discloses that importing Synthesizer takes seconds and creates data directories as a side effect, that files are not opened, and that results exclude symlinks, are sorted, and may be truncated. These details go well beyond a basic list operation.

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 front-loaded with a clear one-sentence purpose, then provides exactly the behavioral details that matter: no opening, import side effects, and result shape. The Returns section is structured and informative without being padded, and every sentence 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?

The description is complete for a no-parameter list tool. It covers success and failure modes, package-missing hints, directory-missing behavior, truncation, symlink exclusion, and sorting. An agent has enough context to invoke the tool and interpret its results without additional documentation.

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 there is no schema burden for the description to compensate for. Per the baseline for 0-parameter tools, this is adequately handled; the description correctly frames the operation as an unconditional listing with no required inputs.

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 and resource: 'List the Synthesizer grid files available on this machine.' It also distinguishes itself from the sibling inspect-like tools by explicitly saying it reports files 'without opening any of them', making its scope clear for an agent choosing a grid.

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 implies when to use the tool: 'so an agent can pick a grid before paying to inspect it.' This clearly situates the tool as a precursor to inspection tools like inspect_local_grid, though it does not explicitly name the alternative or state when not to use it.

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