get_whatsapp_workflow_activity

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states that the tool shows statistics but does not mention read-only nature, permission requirements, or potential side effects. The name implies a read operation, but explicit transparency is missing.

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 very concise, consisting of two short clauses separated by an em dash. It quickly conveys the core function, though the placeholder '[query]' is confusing and could arguably reduce clarity.

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 lack of output schema, the description should explain what statistics are returned, but it does not. It also fails to differentiate from numerous sibling workflow tools, leaving the agent with an incomplete picture of when and why to use this specific tool.

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?

Input schema coverage is 100% with descriptions for all four parameters. However, the tool description does not add extra meaning beyond what the schema already provides. The mention of 'periodo' loosely relates to the 'days' parameter, but no further enrichment is given.

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 that the tool shows execution statistics of WhatsApp workflows within a time period ('Muestra estadísticas de ejecución de los workflows de WhatsApp en un periodo'). It uses specific verbs and identifies the resource, but it does not distinguish from similar sibling tools like get_whatsapp_workflow_logs or get_whatsapp_workflow_stats.

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 no guidance on when to use this tool versus alternatives. It lacks context such as prerequisites or typical scenarios, leaving the agent to infer usage from the name alone.

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