Reporte de crecimiento

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

With no annotations, the description must disclose behavioral traits. It mentions analyzing local SQLite, implying a read-only operation, but does not explicitly state side effects, permission requirements, or the report's return format. This lack of detail fails to inform the agent about important behavioral aspects.

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 a single sentence that immediately states the tool's main function, front-loading the key information. It contains no filler, repetition, or irrelevant details, making it highly concise and well-structured.

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?

Despite the simple parameter set, the description does not explain the output format or the exact contents of the report beyond vague WoW/MoM metrics. Since there is no output schema, the description should have provided more detail on return values, but it remains minimal and leaves substantial ambiguity.

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 single parameter 'dias' is fully described in the schema with a clear explanation (retrospective days to analyze), giving 100% schema coverage. The tool description adds no extra parameter semantics, but the baseline of 3 is appropriate because the schema does all the heavy lifting.

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 uses the specific verb 'Genera' and clearly identifies the resource: a comparative growth report with WoW/MoM metrics, plus the data source 'SQLite local.' This distinguishes it from sibling tools that focus on other aspects like hashtag trends or heatmaps.

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 is provided on when to use this tool versus alternatives. The description only states what the tool does without any exclusions, prerequisites, or comparisons to sibling tools, leaving the agent without explicit usage context.

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