Clonar imputaciones a otro periodo

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

Annotations indicate readOnlyHint=false and destructiveHint=false, but the description does not elaborate on side effects (e.g., whether existing records in the target period are overwritten when replaceExisting is true). No mention of permissions, rate limits, or other behavioral traits beyond the basic copy action.

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?

Single sentence, front-loaded with key information. No fluff or repetition. Could improve by adding brief usage guidance, but remains efficient.

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 6 parameters (5 required) and no output schema, the description is too minimal. It lacks explanation of behavior for replaceExisting, return values, error cases, or examples of epoch ms timestamps. The agent lacks sufficient context to invoke the tool safely.

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 low (33%). The description adds broad context (cloning between periods in epoch ms) but does not explain individual parameters like replaceExisting (boolean with no schema description) or clarify format details beyond what schema already provides for sourceStartTime. The description should compensate for low coverage but 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 clearly states the action (copia/clone), resource (time records), scope (de una persona de un periodo origen a uno destino), and format (epoch ms). It effectively distinguishes from sibling tools like beebole_add_time_record (adds new records) and beebole_delete_time_records (deletes records).

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 on when to use this tool vs alternatives (e.g., adding records individually). No prerequisites mentioned (e.g., person must exist, periods must be valid). Terms like 'replaceExisting' are not explained in the description, leaving ambiguity about behavior.

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