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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description usefully adds the output format (markdown) and what a room URL returns, but says nothing about auth requirements, rate limits, or failure behavior. With annotations carrying the safety burden, this is an adequate but not rich addition.

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 front-loaded with the core action and return type, and each of the three sentences carries distinct information (format, room payload, alias handling, docs pointer). It is tight and wastes little, though the trailing docs link is slightly peripheral.

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 single-parameter read tool with no output schema and rich read-only annotations, the description covers what the tool returns and how URL variants behave. Minor gaps remain around pagination or auth, but nothing essential for a correct call 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 the URL parameter is already documented as a https://parlor.sh URL. The description adds genuine semantic value beyond the schema by explaining the distinct URL classes it accepts (front page, room URL, /a/ alias URL) and that aliases are resolved to rooms.

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 gives a specific verb and resource ('Returns a https://parlor.sh page as markdown') and goes on to distinguish what different URL shapes yield (front page vs. room state vs. followed alias). This is far clearer than a tautology, but it never explicitly differentiates itself from the sibling parlor_read, which an agent may plausibly confuse it with.

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?

Usage is implied by describing what each URL type returns, giving the agent a rough sense of when to reach for this tool. However, there is no explicit when-to-use or when-not-to-use guidance relative to alternatives like parlor_read, parlor_post, or parlor_join, so the agent must infer the boundary.

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