Estado de la cuota de la API

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds critical behavioral context beyond those: the data is derived from SQLite and the tool does not consume API quota, which is non-obvious and important for an agent deciding whether to call it. It also discloses that the reset time is estimated and that local cache state is included.

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 two sentences, front-loaded with the main data points, and ends with a clear safety guarantee. No filler or redundancy; every word earns its place.

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 zero-parameter tool with an output schema, the description fully covers purpose, behavior, and safety. The output schema presumably documents return values, so the description need not repeat them. The only potential missing detail (auth requirements) is unlikely given read-only annotations, making this complete.

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 has zero parameters and the schema is empty with 100% coverage, so baseline for 0 params is 4. The description does not need to add parameter semantics, and it correctly avoids inventing any.

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 explicitly states the tool reports how many REST requests have been spent today, how many remain, the estimated window reset, and local cache state. It uses a specific verb ('Cuantas... se han gastado') and resource (API quota), and it is clearly distinguished from sibling tools which focus on vehicle data, search, or diagnostics.

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 provides clear context for when to use the tool: to check quota status, and importantly that it does not spend quota ('NO gasta cuota'), making it safe to call. It does not explicitly name alternatives or 'when not to use', but all siblings are unrelated to quota, so the usage context is clear. No exclusion conditions are mentioned.

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