list_formats

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

Beyond the readOnly/destructive annotations, the description discloses permission requirements, 403 behavior, that item definitions are excluded, that koumoku_count provides item counts, and that no thinning/sampling is performed. This gives the agent a rich behavioral model of the 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?

The description is concise but information-dense. Every sentence adds a distinct fact: purpose, tenant_id source, permissions, response boundaries, and alternative tool routing. The most important facts are front-loaded.

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?

There is no output schema, so the description partially carries the burden of explaining the response. It clarifies what is not returned and mentions koumoku_count, but it does not enumerate the actual response fields. Still, this is nearly complete for an agent to select and invoke the tool 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 schema already documents all parameters with 100% coverage, so the baseline is 3. The description adds value by explaining where to get tenant_id and by clarifying that 403 errors are about API user permissions rather than parameter correctness.

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 a specific verb and resource: retrieving the list of tenant formats/models. It also explicitly distinguishes itself from list_devices by stating that item definitions are not included, making the purpose clear relative to siblings.

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?

It gives explicit guidance: obtain tenant_id from list_tenants, requires system administrator level, and 403 should be interpreted as a permission problem rather than a parameter problem. It also names the exact alternative, list_devices with include_format_detail=true, when item definitions are needed.

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