list_styles

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the result as a 'canonical list,' implying authority and completeness, but it does not disclose whether the list is static or fetched live, or if there are any side effects. The verb 'Return' suggests a read-only operation, but this is not explicitly stated.

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 sentence that is clear and concise, with no redundant language. The parenthetical '(Nano Banana Pro AI)' adds contextual brand identification without unnecessary detail, making it highly efficient.

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 tool has no parameters and no output schema, the description sufficiently explains the return value as a list of style presets. It could mention the format or structure of the list, but for a simple parameterless lookup, the description is adequately complete.

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, and the schema coverage is 100% (vacuously). The description provides all necessary context for a parameterless call, and no additional parameter meaning is needed. This aligns with the baseline of 4 for parameterless tools.

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 clearly states the tool returns a canonical list of image-generation styles or presets, using a specific verb ('Return') and resource. It distinguishes itself from sibling tools like get_pricing and get_official_links by focusing on styles, making its purpose unambiguous.

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 usage by stating what the tool returns, but it does not explicitly explain when to use this tool versus alternatives or mention exclusions. The sibling tools suggest a category of informational lookups, but no direct when-to-use guidance is provided, so usage is only implied.

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