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

With no annotations, the description carries the full burden. It discloses that groups are public by default, that isPublic=false makes them invite-only, and that a slug is derived from name if omitted. However, it omits other behavioral aspects like permissions, idempotency, or failure modes. More importantly, the schema shows zero properties, contradicting the parameter references in the description, which confuses the behavior.

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 concise, with two sentences that front-load the main purpose and then add relevant details. The structure is logical and free of filler, though the parameter references are misleading given the empty schema, slightly detracting from clarity.

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?

The tool cannot be correctly invoked because the schema doesn't support the described parameters. There is no output schema, so the agent doesn't know what the tool returns. The description leaves critical gaps about required arguments and response format, making it incomplete for a creation tool.

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?

The input schema has zero properties, yet the description references parameters like kind, recipient handle, isPublic, name, and slug. The agent cannot supply these parameters because the schema doesn't allow them. The description does not align with the schema and provides no actionable parameter meaning. This is a critical failure.

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 clearly states the tool creates a DM or a group room, naming the specific action and resource. It distinguishes between the two types and gives relevant details (public vs invite-only, slug derivation), making the purpose unambiguous.

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 explicitly states when to use the tool (to create a DM or group) and provides context about default behavior (public groups, isPublic flag). However, it does not mention when not to use it or point to alternatives, though the sibling set offers no direct creation alternative. Clear enough for most cases.

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