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

The description is consistent with the annotations (readOnlyHint=true, destructiveHint=false, openWorldHint=false) and reinforces them with 'opens nothing by itself', which is the single most important thing to know about a tool named 'list'. It also discloses the output shape (guidance, not data) and the required hand-off to browser tools, plus the fact that Hostfully has no official MCP server, explaining why a browser path is needed.

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?

Purpose and behavior are front-loaded well, but the middle sentence is convoluted ('Returns how to do it in Hostfully step by step... and opens nothing by itself; then do it with...') and crams three ideas into one clause. The trailing note about the Open API v3 and the dated 'no official MCP server' check is useful justification but secondary to invoking the tool.

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?

For a zero-parameter, annotation-covered, no-output-schema tool, the description covers what an agent needs: what comes back, that nothing is opened, and which tools complete the task. It does not address whether the guidance is scoped to a specific workspace or account selection, which is the main remaining unknown.

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?

The tool takes zero parameters, so there is nothing to specify and the description is not required to compensate. The baseline for a no-parameter schema applies.

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 names a specific resource and scope ('properties in the user's own Hostfully account') and then discloses the actual return: step-by-step screens, buttons and fields rather than property data. That clarification is the key disambiguator, though the opening phrase 'List properties' sits in mild tension with the how-to nature of the output, and no sibling (e.g. hostfully_list_reservations) is contrasted.

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 explicit sequencing: this tool returns instructions and 'opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Hostfully Cloud Browser', so the agent knows the workflow this tool starts and what must follow. It stops short of stating prerequisites or when another hostfully_* tool would be the better choice.

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