fb_list_generators

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

With no annotations, the description carries the full behavioral burden. It conveys that this is a read/list operation and discloses the session-database default plus an ambiguity protocol (ask the user when multiple DBs exist and none is active). It omits permission/prerequisite requirements and any hint about result shape, which matters since there is no output schema.

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?

Two short sentences, front-loaded with the core action and followed by the one necessary caveat about database selection. No filler; only the missing alias-discovery detail keeps it from being maximally tight.

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 single-optional-parameter list tool with no annotations or output schema, the description covers what is listed, the parameter's meaning and default, and the multi-database ambiguity case. Only the return format and alias discovery are left implicit, which is acceptable at this complexity.

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?

Schema coverage is 0%, so the description must compensate, and it largely does: "no banco especificado (ou ativo na sessão)" explains that db_alias selects a database and that the parameter is optional because the session-active database is used as the fallback. It stops short of stating the alias format or how to discover valid aliases.

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 ("Lista") and a precise resource ("Generators / Sequences de usuário"), scoping it to a database. This clearly separates it from siblings such as fb_list_tables, fb_list_views and fb_list_procedures, which target different object types.

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 real usage context: list generators in the specified database or the session-active one, and ask the user when several databases exist and none is active. It does not name alternative tools (e.g., fb_list_databases first, or fb_use_database to set the active DB), so it stops short of full routing guidance.

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