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

No annotations are provided, so the description carries the full burden of behavioral disclosure, and it discloses nothing: not whether it produces a plan object, whether it is read-only, what the output looks like, or how it treats the intent options. A pure name restatement.

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?

It is short, but that brevity is under-specification rather than conciseness; the single sentence is a namespace-qualified name with no descriptive content.

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?

A planning tool with two semantically rich enum parameters, no annotations, no output schema, and a 0% parameter description is left completely unexplained. The description gives the agent nothing needed to call it correctly or interpret its result.

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%, so the description must compensate, yet it says nothing about the intent enum values (compare, participant-leave, host-preserve, host-end, rejoin) or what targetSdk means. The enum labels hint at semantics, but the planner's interpretation of each intent and whether targetSdk is required or defaulted goes unexplained.

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 only restates the tool name and an internal alias ('room-lifecycle-planner'); it never states what the tool actually does. An agent learns nothing from it beyond 'lifecycle plan', which is essentially a tautology of the name. It is not distinguishable from siblings such as shared::room.authority.plan or shared::lifecycle.cleanup.audit by description alone.

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?

There is no when-to-use guidance, no mention of alternatives, and no exclusions. The agent has no basis for choosing this over the many sibling planning tools.

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