Consolidated AR Aging (Gestoria)

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

Annotations already mark it as read-only and idempotent. Description adds specifics like return structure (buckets, breakdown, top invoices) and scope requirement for different ownerUid. Adds context beyond annotations without contradiction.

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?

Two bilingual sentences front-load key functionality and parameters. Every word is informative. No waste.

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?

Given the tool's moderate complexity and existence of an output schema, the description covers purpose, parameter usage, behavioral notes, and expected output structure. Sufficient for an agent to correctly select and invoke.

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 coverage is 100% for the single parameter. Description explains default behavior and scope requirement, adding significant meaning beyond the schema definition.

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 tool retrieves a cross-client AR aging report for a gestor, with details on bucketing (current, 30-60, 60-90, 90+ days) and breakdowns (per-workspace and top invoices). It distinguishes from siblings as no other tool provides this specific report.

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?

Explicitly states default behavior (authenticated gestor) and how to query a specific gestor via ownerUid with elevated scope. Clear when to use each mode, though no explicit mention of alternatives among siblings.

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