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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered structurally. The description adds valuable context by naming the required financials:read scope and stating that the tool is unavailable under the current authorization, though it also redundantly repeats 'Efeitos: Nenhum' and does not describe pagination or result limits.

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 compact and front-loads the returned resource before the scope and availability note. The second line includes some boilerplate that partly repeats annotation information, but no sentence is seriously bloated.

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 read-only listing tool with no output schema, the description supplies the key returned attributes and the authorization status. It still omits sibling routing and pagination behavior, but annotations and the input schema cover the remaining safety and filter basics.

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 67%, with dates documented in the schema and kind exposed as an enum. The description mentions the period and financial entry categories, but it does not map those categories to the kind enum or clarify filtering behavior beyond what the schema already provides.

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 resource: received payments, expenses, refunds and cash movements for a period, including method, operator and stay linkage. This is more specific than the tool name alone, but it does not explicitly distinguish the tool from nearby siblings such as get_cashflow, list_balance_due or list_guest_bills.

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 period scope is implied and the authorization note signals when the tool is unavailable, but there is no explicit guidance on when to choose this tool over get_cashflow or other financial listing tools. The agent must infer the use case from the resource description.

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