outlook_agenda_hoje

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

With no annotations, the description carries the burden of behavioral disclosure. It states the tool returns events, implying a read operation, but does not specify nuances such as whether it includes all-day events, timezone handling, or whether it covers events that started before today but end today. It is adequate but minimally transparent.

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, concise sentence that immediately conveys the tool's function. It is front-loaded and contains no extraneous information, making it highly 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?

The tool has low complexity (0 params, no output schema) and no annotations. The description provides the core behavior but omits important contextual details such as the scope of events (all calendars vs. default), date-range boundaries, and how results are structured. An agent might not know how to interpret the output without additional information.

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 tool has zero parameters, so schema coverage is trivially 100%. According to the rubric, a 0-parameter tool gets a baseline score of 4. The description adds no parameter-related details because there are none to explain, which is appropriate.

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 verb 'returns' and the resource 'today's events in the Outlook calendar', making the tool's purpose unambiguous. It naturally distinguishes itself from sibling tools like outlook_agenda_semana (week) and outlook_detalhes_evento (event details) by specifying 'today'.

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 explicit guidance on when to use this tool versus alternatives. While the name and description imply it is for today's agenda, there is no mention of when not to use it or that outlook_agenda_semana should be used for weekly views. The guidance is entirely absent.

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