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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint. The description adds valuable behavioral details: results are ordered by start time, truncated at 50, day filter applies only to live bookings, and membership requirement. These details go beyond annotations without contradiction.

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 concise, consisting of two sentences that front-load the main action. It avoids redundancy and includes necessary details without fluff. A slightly more structured layout could improve readability, but it is efficient as is.

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 no output schema, the description lists the fields returned (space, slot, status, event, host) and notes ordering, truncation, and membership requirement. It captures the essential context an agent needs to understand the tool's behavior and output. Minor improvements could include more detail on the limit parameter.

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, the description must explain all parameters. It describes space_id, day (with format and scope), status, and community_id (implicitly required). However, it does not explicitly mention the 'limit' parameter, only hinting at truncation. Most parameters are covered, but one is missing, resulting in a moderate score.

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 lists venue bookings for a community and specifies the fields returned (space, slot, status, event, host). It is distinct from sibling tools like list_events or list_spaces, though it could explicitly differentiate itself. Still, it achieves clarity with a specific verb and resource.

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 mentions prerequisites ('Members only', 'Requires community_id') but provides no guidance on when to use this tool versus alternatives. It does not list exclusions or direct users to other tools for different scenarios, limiting its helpfulness for tool selection.

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