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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description agrees with a terse 'Read-only.' Beyond that, it discloses the substance an agent actually needs: the 30% commission rule, that it accrues for as long as the client pays, and the four reporting lenses (month, year, pending, paid out) plus per-client granularity. It does not state whether it requires an authenticated gestoría role or what the currency/format of the figures is, so it falls short of full transparency.

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 audience ('For a gestoría account') and the subject ('what it earns from contix'), with the commission model in a parenthetical. It is dense but every clause carries meaning; the trailing 'Read-only.' is small redundancy against annotations but harmless.

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 parameters, no output schema, and safety covered by annotations, the description carries the return-value burden well by enumerating the periods and per-client breakdown. It is nearly complete for a zero-argument read report; only the units/format of the amounts and any gestoría-role prerequisite are unstated.

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 tool takes zero parameters, so the schema imposes no semantic burden and the baseline is 4. The description correctly implies no input is needed, keeping the call shape unambiguous.

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 names a specific resource (a gestoría's earnings from contix) and specifies the exact commission model (30% of each linked client's net monthly fee) plus the breakdown windows. An agent can immediately tell this is a commission/earnings report. It stops short of naming or contrasting any sibling such as gestoria_resumen_mandante, which is the closest alternative.

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?

Usage is only implied by the qualifier 'For a gestoría account', which signals the prerequisite context but not when to pick this over related gestoría reporting tools. There is no explicit when/when-not, no mention of prerequisites like an active mandante mandate, and no alternative named.

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