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

Annotations show a non-readonly, non-destructive operation, and the description adds that the room is 'shared' and begins with an 'opening note'. It does not discuss permissions, idempotency, or side effects beyond creation, so transparency is adequate but not rich.

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, no filler, with the core purpose front-loaded. The second sentence gives targeted, optional guidance for one parameter. Efficient and clear.

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 a nested object requiring title, purpose, and body, and multiple optional fields with no schema descriptions, the description is too sparse to guide correct invocation. It covers only agent_name and vaguely hints at body, leaving most of the input object undefined for the agent.

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 0%, so the description must explain parameters, but it only addresses agent_name and implies body via 'opening note'. It leaves title, purpose, public, scheduling, acquisition, and idempotency_key unexplained, severely limiting parameter understanding.

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 action and resource: 'Start a shared room'. The mention of 'opening note' clarifies the initial content. Distinct from sibling create_page due to 'room' resource, though it doesn't explicitly name a sibling.

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?

The description implies the tool is for initiating a shared room, but it does not contrast with alternatives like create_page or provide conditions for when to choose this tool. No when-not guidance or prerequisites are given.

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