analytics_alerts

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

With no annotations, the description must carry all behavioral transparency, but it provides none. It does not mention side effects, permissions, return types, or any side effects, making it impossible to understand what the tool does beyond a generic label.

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 extremely short, which is concise, but it sacrifices clarity. It lacks any structural elements like verb-first phrasing or scoping, making it ineffective despite its brevity.

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?

The tool is severely incomplete: no parameter descriptions, no output schema, and no mention of expected results. The description does not provide enough context for an agent to use the tool correctly.

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 only parameter 'fields' is a string with no description in the schema, and the tool description does not explain its purpose. There is zero semantic information about what fields are expected or how they influence the tool's behavior.

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 'Alertas analiticas y recomendaciones' is vague and does not specify a clear action or resource. It fails to distinguish this tool from siblings like analytics_waros or analytics_cohort, providing only a broad notion of alerts and recommendations.

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 given on when to use this tool versus alternatives. The description lacks any conditional statements, use cases, or exclusions, leaving the agent without direction for selection.

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