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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the non-destructive nature is covered. The description adds genuinely new context: the NOMADSTAYS_MCP_AGENT_TOKEN auth requirement and the all-or-nothing fileNames constraint, which the annotations do not carry.

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 tight sentences: purpose first, then the operational constraint, then the auth requirement. Every sentence earns its place and nothing is redundant.

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?

No output schema exists, but for a pure reorder operation the description covers prerequisite, constraint, and auth. Nothing an agent needs to invoke it correctly is missing.

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%, so baseline is 3, but the description stresses the critical semantic that fileNames must be the FULL current gallery with the same set of files, which is the most error-prone aspect of the call. This adds emphasis beyond the schema text.

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?

States a specific verb (change the display order) and resource (a Stay's listing or workspace photo gallery), and its scope is clear enough to separate it from getMyStayPhotos and the sibling reorderRoomPhotos. An agent knows exactly what operation this is.

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?

It gives the prerequisite (call getMyStayPhotos first) and the boundary ('only reorders; it cannot add or remove photos'), which routes the agent to uploadStayPhoto/deleteStayPhoto for those needs. No alternative is named explicitly for those add/remove cases, so it stops just short of a 5.

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