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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds value by revealing the auth requirement (NOMADSTAYS_MCP_AGENT_TOKEN), the resolved-to-names behavior for facilities, and the inclusion of viewable CDN URLs for photos. These details go beyond annotations, though it doesn't mention pagination or error behavior.

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?

Three sentences, each earning its place: purpose + return contents, usage timing + benefit, and auth requirement. No fluff or repetition, with key information front-loaded.

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?

With no output schema, the description compensates by listing the main fields returned (bed setup, occupancy, facilities, photo URLs) and hints at roomId/fileName availability. It's a simple one-parameter tool, so this is fairly complete. Could be improved by explicitly stating the return is an array of rooms, but the wording 'List all rooms' implies that.

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 coverage is 100% with stayId described as 'The Stay's EntryID (use getMyStays to find it).' The description doesn't add anything about the parameter itself, relying on the schema. This matches the baseline for full schema coverage.

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 opens with a specific verb and resource: 'List all rooms currently configured on one of your Stays.' It goes beyond a simple list by enumerating the returned data (bed setup, occupancy, facilities resolved to names, photo CDN URLs), which distinguishes it from sibling tools like getMyStayDetail or getMyStayPhotos. The mention of being a prerequisite for room mutation tools further clarifies its unique role.

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?

Explicitly states when to call: 'Call this before createStayRoom, updateStayRoom, deleteStayRoom, deleteRoomPhoto, or reorderRoomPhotos.' It also explains the benefit: 'so the agent can show current values or find the right roomId/fileName.' This provides clear, actionable guidance and implicitly differentiates from the mutation tools.

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