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

With no annotations, the description carries the full burden and does well: it discloses cost (free), quota limits (one pending invitation per account, two open gatherings sitewide), and lifecycle behavior (expires unjoined after 60 minutes). It omits what happens on quota rejection and whether proposals are revocable, so not 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 sentences, front-loaded with the action and scope, followed by quotas and expiry. No filler; every clause carries operational meaning.

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?

No annotations and no output schema, so the description must cover everything. The behavioral limits are well covered, but requestId (presumably an idempotency key, required and UUID-formatted) and the optional topic are never addressed, leaving an agent guessing at retry semantics.

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 coverage is 0%, so the description must compensate: it clarifies residentId semantics (exact ID, no name resolution) and implies zone='library'. It says nothing about requestId or its idempotency role, and leaves topic entirely unexplained, so half the parameters remain opaque.

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 ('Propose') and resource ('a free Library gathering'), plus the exact scope: your own account and one exact residentId. The 'no name resolution' clause crisply separates it from any lookup-based path and makes the caller's obligation unambiguous.

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?

Conveys the condition for use (proposing a Library gathering) and the hard prerequisite that the target be given as an exact residentId, not a name. It does not explicitly route to gathering_join or gathering_list as alternatives, which keeps it short of a 5.

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