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

Annotations only provide false hints for readOnly, idempotent, and destructive, which is ambiguous. The description adds the explicit '[write, altera dados]' tag, making the mutating nature clear. It also identifies the affected object as a global system configuration value, but it does not disclose broader impact, permissions, or potential side effects of altering a global setting.

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 with the operation front-loaded, followed by the endpoint and a concise side-effect tag. There is no filler or redundancy. The structure is clean, though additional parameter context would be needed for full usefulness.

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 write tool with zero parameter documentation, no output schema, and no explanation of what body, query, or account mean, the description is insufficient for correct invocation. It states the intended purpose but leaves the agent unable to construct a valid request.

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%, and the description does not mention body, query, or account at all. With three string parameters and no required fields, an agent cannot determine what payload, query string, or account identifier to provide. The endpoint path is the only meaningful clue about how to invoke this tool.

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 action ('Alterar valor') and the resource ('configuração global do sistema'), and includes the endpoint POST /ini/postconfig. The 'Condomínios:' prefix adds domain scope. However, it does not differentiate itself from similar configuration-related siblings such as superlogica_ini_config or superlogica_configuracoes_*.

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 this tool is used to change a global system configuration value, but it gives no explicit when-to-use guidance, no exclusions, and no mention of alternatives. With many configuration-related sibling tools, an agent receives no help deciding between this and similar options.

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