glpi_listar_config

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

No annotations provided. Description implies read-only operation ('Lista') but does not explicitly state it is non-destructive, safe, or discuss authentication/rate limits. For a list tool, more transparency about side effects is expected.

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 sentences, front-loaded with purpose, then parameter behavior. No unnecessary words. Efficient and clear.

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 list tool with one optional parameter and no output schema, the description is mostly complete. It explains the parameter effect and overall function. Lacks return format (e.g., list of names or key-value pairs), but that is a minor gap.

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 description must compensate. It clearly explains that the 'context' parameter filters to that context when provided, and lists all contexts when absent. Adding an example (e.g., 'core') helps, but could mention valid values or format.

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?

Description states tool lists configuration parameters and explains behavior with/without 'context'. It distinguishes from sibling tools like glpi_consultar_config (single config) and glpi_atualizar_config (update), but does not explicitly name them.

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?

Provides clear usage: without context lists all contexts, with context lists parameters of that context (e.g., 'core'). Does not specify when not to use or mention alternatives like glpi_consultar_config for a single parameter.

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