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

Annotations already declare this is a read-only, non-destructive, closed-world read. The description adds genuinely new behavior: with a jobId it blocks/wait up to 40 seconds for the publish to complete, which is a significant trait an agent needs to plan around. It does not disclose what happens on timeout, which keeps it from a 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?

Two sentences, front-loaded with the primary payload description, and the conditional jobId behavior is separated into its own sentence. The first sentence is a long parenthetical list but every element maps to a real return field, so little is wasted.

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 usefully enumerates the return fields, which is exactly what compensates for that gap. Remaining holes are timeout/failure behavior and the meaning of the required projectId, but the core contract for calling it correctly is present.

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 50%: jobId is documented in the schema and further enriched in the description (source tool, 40-second wait), but projectId is bare in the schema and entirely unexplained in the description. The description adds value for one param while leaving the required one undocumented, matching a baseline 3.

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 states concretely what the tool reports: the project's EmDash CMS site (address, live/offline, setup completion, admin access), any static deploy, and whether the account is connected to Cloudflare. That is specific enough to distinguish it from most siblings, though it never explicitly contrasts itself with the similarly named uichemy_publish_status or uichemy_site_admin_login, which is the main ambiguity left.

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 says the jobId comes from uichemy_publish_emdash "while a publish is running," which gives implied guidance for the polling use case. Beyond that there is no explicit when-to-use/when-not-to-use guidance and no routing away from alternatives such as uichemy_list_sites or uichemy_publish_status.

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