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

Annotations already declare readOnlyHint=true and openWorldHint=false, but the description adds meaningful behavioral context: environment-dependent routing between Mac app and statuz.cloud, that it 'says where' it opened, and that cloud items do not auto-open remotely. It stops short of covering permissions or failure modes, so a 4 rather than 5.

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?

Front-loads the core action ('Show the person a post or a page') and keeps the routing caveats compact. It is slightly dense with backticked commands but every sentence carries operational meaning; minor trimming could improve flow.

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 no output schema and a read-only, environment-sensitive tool, the description explains local vs cloud behavior, what it reports ('says where'), and the cloud-agent alternative (`links.web`). It is nearly complete, though an agent might still wonder about error behavior when the Mac app is absent.

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 description coverage is 100%, so the schema already documents `org`, `page` (including the billing cloud-only note), and `post`. The description mentions 'post or a page' but adds no syntax, formats, or precedence rules beyond the schema, so baseline 3 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?

States a specific verb ('Show/Open') and resources ('post or a page'), plus the routing condition (Mac app if installed, else statuz.cloud). This clearly distinguishes it from sibling read tools like posts_get or posts_list, which fetch data rather than open it for the person.

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 says when to use it (opening a post/page on this computer), when behavior differs (cloud-only items, 'Statuz Cloud opens nothing by itself'), and what to do instead for cloud agents (give the person `links.web`). This is a clear when/when-not with an alternative.

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