fb_reload_config

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

No annotations are provided, so the description carries the full burden. It says where the config is read from but not what happens on reload (does it overwrite in-memory state, replace the connection pool, fail on malformed files, take effect immediately?), nor does it state the precedence between global and local sources despite listing both.

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?

One sentence, front-loaded with the action, and no filler. Slightly under-specified rather than overly padded, but structurally sound.

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?

With no annotations, no output schema, and an undocumented parameter, the description should describe the reload's effect and result. It leaves the agent without knowing what changes after the call or how to detect success.

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 description coverage is 0% for the single 'config_path' parameter, so the description must compensate. It hints at the source choices ('Catálogo Central Global' vs 'arquivo local do projeto') but never connects them to config_path, its expected format, or what a null default implies.

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?

States a specific verb ('Recarrega') and resource ('configuração de bancos') and names two distinct sources (global catalog ~/.firebird-mcp.json or project-local file), which is clearer than a bare reload tool. It does not, however, distinguish itself from siblings like fb_create_config or fb_use_database, so an agent must infer the reload-vs-create-vs-select boundary.

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?

There is no explicit when-to-use guidance, no mention of prerequisites (e.g. after editing the config file), and no named alternative among the siblings. Usage context is only weaky implied by 'a partir do Catálogo Central Global'.

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