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

With no annotations, the description carries the full behavioral burden. It does not state whether this is a read-only operation, how long an environment typically remains in a transient state, whether component_urls_json is only populated once provisioning completes, or how often the caller should poll. Only the vague verb 'Poll' hints at repeated invocation.

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?

A single short sentence with no filler, front-loaded with the act (poll) and the target (BunnyShell environment status). It is efficient but under-specified rather than well-structured.

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?

One required parameter is undocumented, no output schema exists, and no annotations are present, so the description is the only specification an agent has. It omits the parameter semantics, safety profile, return content (beyond a cryptic JSON name), and polling guidance, leaving the tool under-specified.

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 0% and the single required parameter 'bnsEnvironmentId' has no description, so the description must compensate but does not. It never mentions the parameter, its format, where the ID comes from, or whether it is the environment ID returned by provision-ephemeral-environment.

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 restates the tool name: 'get-ephemeral-environment-status' → 'Poll BunnyShell for environment status'. The addition of 'component_urls_json' is the only real information, and it's an ambiguous internal artifact name rather than a description of what data is returned. It does not distinguish this from siblings like list-bunnyshell-environment-events.

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?

No when-to-use guidance is given. The word 'Poll' weakly implies a repeated-check pattern, but the description does not say when to call this versus provision-ephemeral-environment-and-wait (which presumably also yields readiness) or list-bunnyshell-environment-events. No exclusions are stated.

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