events_of_today

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

Indicates read-only operation (return items) and auth V1+V2, and notes multi-value filter behavior, but does not disclose rate limits, side effects, or default behaviors for null parameters.

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?

Two sentences plus compact metadata. Front-loaded purpose and key usage hint (multi-value filters). Efficient but could be slightly clearer with parameter grouping.

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?

For a tool with 10 optional parameters, no output schema, and no annotations, the description leaves many gaps: date format, filter semantics, time range interpretation, limit truncation, etc. Incomplete for confident usage.

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?

With 0% schema coverage, description adds minimal parameter insight: only a generic note on multi-value filters. No explanation of local_date, project_ids, text_query, time_from, time_to, limit, etc.

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 it returns timed scheduled items for a given local day, with category and related tools listed, distinguishing it from siblings like tasks_of_today and query_agenda.

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?

Mentions related tools (tasks_of_today, query_agenda) and that multi-value filters accept list or string, but lacks explicit when-to-use or when-not-to-use guidance.

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