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

The annotations already indicate this is a non-destructive write operation in a closed world. The description adds useful access-control context by limiting use to the room card, but it does not explain idempotency, expected effects, or failure 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?

Two short sentences with no waste: the action is front-loaded and the access restriction follows immediately. Every sentence contributes to understanding the tool.

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?

For a simple one-parameter mutation tool with annotations and no output schema, the description covers purpose and access. It still leaves the parameter meaning and duplicate-call behavior unspecified, which would help an agent invoke it correctly.

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?

There is one required parameter, room_id, with 0% schema description coverage. The description mentions 'room card' but does not clarify what room_id represents, its expected format, or how it relates to the recorded invitation copy.

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 a specific verb and event: recording that the room card copied a guest invitation. It is clearly distinct from sibling game-room tools, though the term 'room card' is somewhat contextual rather than fully self-explanatory.

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 gives an explicit eligibility restriction: only the room card can use this tool. However, it does not state when an agent should call it versus alternatives or what conditions trigger the recording.

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