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

Annotations already flag this as a non-read-only, open-world operation, and the description adds real context on top: it emails the visitor, it reaches other people requiring user confirmation each call, the confirmation default can be switched off, and it needs a Cotlet API key with app access. These are meaningful side-effect and auth disclosures beyond the structured hints.

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?

Purpose is front-loaded and the key side-effect/auth warnings are present. There is minor redundancy between "sent to the visitor by email" and "emails the code and instructions to the visitor," but the sentences otherwise earn their place.

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 mutation tool that sends an email, the definition covers the external-recipient side effect, the confirmation policy, and the required credential, none of which the annotations express. With no output schema and full param coverage, the remaining omission is only the response shape, which is minor.

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 100%, so the schema already documents all six parameters, including property_id sourcing from list_properties. The description only loosely restates the one-person/one-day constraint and adds no format or syntax detail beyond the schema, so baseline 3 applies.

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 verb (creates) plus resource (Visitor Access Code) and scopes it precisely: one person, one day, one property. An agent can distinguish this from sibling rently tools like grant_safe_mode_access or send_self_tour_invite without opening the schema.

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?

"Use it for vendors, inspectors or agents who need to enter once" gives a clear when-to-use criterion with the intended audience. It stops short of naming an explicit alternative sibling or a when-not-to-use case, so it falls just below the top bar.

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