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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the read-only behavior is covered. The description adds the location (/tools) and the public/free scope, but it does not disclose additional behaviors such as whether the list is complete, ordered, or paginated.

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 a single concise sentence that contains the essential action, object, and location. Every word adds value, and the most important information is 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?

Given zero parameters, safe read-only annotations, and the presence of an output schema, the description is mostly complete for invoking the tool correctly. It could briefly mention that this is the discovery entrypoint for run_free_tool, but this is a minor gap rather than a functional omission.

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 there is nothing for the description to explain about inputs. The baseline for zero-parameter tools applies, and the description sufficiently identifies what is being listed.

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 states a specific verb (List) and resource (public free tools at /tools), making its function immediately clear. It also distinguishes itself from the many list_* and run_free_tool siblings by narrowing the scope to public free tools.

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 gives clear context that this lists public free tools, but it does not explicitly state when to prefer it over related tools like run_free_tool or list_public_generations. Usage is implied rather than directly guided.

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