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

Annotations already mark this as a non-read-only, open-world, non-destructive action, so the bar is lower. The description adds real behavioral context beyond the annotations: the invite link expires after 15 minutes, the call reaches an external person requiring user confirmation, and a Cotlet API key with app access is required. It still doesn't say whether the invite can be revoked or what happens on failure, keeping it below a 5.

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 materially redundant: the purpose statement and the 'invite link is valid for 15 minutes' claim are each stated twice in near-identical wording. This duplication bloats the definition without adding information, which is the opposite of front-loaded conciseness.

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 send-action tool with no output schema, it covers the important non-obvious facts: external recipient side effect, confirmation requirement, link expiry, and auth needs. The only real gap is that it never mentions the property/lead context needed to make a valid call, but the schema covers that.

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% with all five parameters documented in the schema, so the schema carries the semantics. The description adds no parameter-level detail (e.g. how tour_at should be formatted or where property_id comes from), giving the baseline 3.

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 resource: inviting a prospect to self-tour a unit at a set time, scoped to multifamily properties. The scope qualifier '(multifamily)' meaningfully narrows the tool. It does not, however, name any sibling (e.g. rently_set_self_touring, rently_assign_lead) to differentiate itself from alternatives in the large Rently family.

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 procedural guidance ('By default you confirm each call; you can switch that off' and 'Reaches other people: confirm with the user before each call'), which is genuinely useful. However, there is no when-to-use-this-instead-of-alternative guidance and no prerequisites around the lead/property state, so usage is only implied.

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