events_attendee_schedule

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

No annotations are present, so the description must disclose behavioral traits. It fails to mention that the tool is read-only, what happens if the person is not found, or any limitations (e.g., maximum events). The description only lists parameter formats.

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 tightly written: one sentence for purpose followed by concise parameter descriptions. Every sentence adds value, and it is structured for quick scanning.

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 tool has an output schema (not shown), return values are presumably covered. However, the description lacks behavioral details (e.g., read-only, pagination, authentication) and does not address edge cases. It provides adequate parameter info but lacks completeness in usage context.

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?

Schema description coverage is 0%, meaning the description must compensate. It provides meaningful guidance: person parameter with example names, date parameters with YYYY-MM-DD format hints, and default values for year and start_date. This adds significant value beyond the schema titles.

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 'Show all events a specific person is attending,' which is a specific verb-resource pair. It distinguishes from sibling event tools like events_search (general search) and events_upcoming (upcoming events) by focusing on a specific person's schedule.

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 parameter details and defaults but does not explicitly state when to use this tool versus other event tools. It implies usage for per-person queries but lacks alternatives or when-not conditions.

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