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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds the sorting order ('Sorted Location → floor → name') and the scopef of data (bookable venue Spaces). There is no contradiction with annotations.

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, well-structured paragraph that efficiently conveys purpose, output fields, sorting, and conditions. Every sentence adds value, and it is not verbose.

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?

In the absence of an output schema, the description lists all returned fields (name, Location, floor, capacity, etc.) and explains permissions and required parameters. It fully covers what the agent needs to know to use the tool correctly.

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 description coverage, the description must compensate. It explains that community_id is required and include_archived is optional, but does not elaborate on the meaning of community_id beyond 'requires community_id'. It adds some context but could be more explicit about the parameter purposes.

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 'List a community's bookable venue Spaces' with a specific verb and resource. It enumerates the returned fields (name, Location, floor, etc.) and distinguishes the tool from siblings like list_events or list_guests.

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 specifies the conditions for use: 'For members, active-deal partners, or anyone in an open community.' It also notes the required parameter and optional include_archived. It does not explicitly contrast with other list tools, but the context is clear.

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