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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds the GET method and confirms this is a listing operation, which is consistent with the annotations, but it does not disclose pagination, authentication requirements, or response characteristics.

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 compact sentence with the key operation and endpoint front-loaded. There is no filler, repetition, or unnecessary detail; every word contributes to basic understanding.

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?

The tool is a simple list operation, but the description is thin for safe invocation: parameter meanings are entirely absent, no output schema exists, and there is no mention of how the optional query/account params affect results. An agent would likely need external documentation to use this correctly beyond the basic endpoint.

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 schema has 0% description coverage and the tool description does not mention the query or account parameters at all. With two undocumented optional parameters, the description needed to compensate by explaining their meaning or usage, but it does not.

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 (Listar), a clear resource (áreas comuns), and the HTTP endpoint (GET /reservas/areas). This distinguishes it from sibling reservation tools such as superlogica_reservas_create or superlogica_reservas_areasreservas, which operate on reservations rather than listing common areas.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, intended use cases, or exclusions, so an agent gets little help deciding between this and other reservation-related endpoints.

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