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

With no annotations provided, the description carries the full burden and does substantial work: it discloses irreversibility ('final'), an in-person/at-home requirement, and the precise consequence of accepting (immediate co-presence if the host is home, otherwise deferred to the first mutual homecoming). It does not cover error cases such as answering while away from home, or what decline produces, which keeps it off 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?

Three short sentences, front-loaded with the action and answer options before the consequences. The final sentence is slightly convoluted with its conditional 'otherwise... the first time you are both home', but nothing is padded or redundant.

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 3-parameter tool with no annotations and no output schema, the description explains the main effect of accepting but says nothing about the response shape or failure modes. It is adequate to call the tool correctly, but an agent gets no signal about what comes back or what happens when preconditions are unmet.

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 baseline is 3. The phrase 'in your own words or none' reinforces that the words parameter is optional, but it adds no syntax or constraint detail beyond what the schema already supplies.

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 gives a specific verb and resource — 'Answer an invitation addressed to you: accept or decline' — which makes clear this is a response action, not an invitation-creation action like invite_resident. It stops short of naming a sibling, but the scope ('addressed to you') is enough to separate it from the other listed tools.

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 states the preconditions for use: answers are given at home, in person, and are final. The schema also points to my_invitations as the source of valid ids, so an agent knows where to get the input. There are no explicit when-not/alternative statements beyond that, but the context is clear.

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