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

Beyond annotations (which show readOnlyHint=false), the description adds that the address is 'stamped onto events at booking confirm' and hours are 'soft policy'. However, it does not detail exact side effects, authorization nuances, or idempotency.

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, using a single packed sentence plus two short statements. It front-loads the purpose and key attributes. However, the first sentence could be split for better readability.

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 11 parameters, no output schema, and minimal annotations, the description covers most relevant fields but omits the 'description' parameter and does not discuss return values or error conditions. It provides adequate context for a creation tool.

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 compensates by listing many fields (name, location_name, floor, capacity, etc.) with brief explanations. But it misses the 'description' field and does not explain formats for complex types like photos or hours.

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 'Add a bookable venue Space (room/floor)' with a specific verb and resource. It lists the main fields and notes admin-only access. However, it does not explicitly distinguish this tool from siblings like update_space or set_space_status.

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 'Admin-only' and 'Requires community_id + name', giving basic context. But it lacks explicit guidance on when to use this tool versus alternatives (e.g., update_space for modifications) or when not to use it.

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