End a presence

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

With no annotations, the description carries the full burden. It discloses that the operation is 'clean' and frees a slot, implying it's not destructive in a harmful way but is a cleanup action. It does not mention any side effects like throwaway resources, idempotency, or failure behavior, so it's adequate but not rich.

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 two sentences with no filler. The first sentence is front-loaded with the verb and purpose, and the second provides the usage guidance. Every word earns its 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 simple one-parameter cleanup tool, the description is complete enough. It explains the lifecycle context (step 3 of 3), the benefit (frees slot), and the necessity (concurrency cap). It does not detail the output or error states, but given no output schema and the clear action, this is sufficient.

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 only one parameter, presenceId, with 0% schema description coverage, but the description implies it identifies the presence to retire by referencing 'a presence created by spawnPresence.' It doesn't state that presenceId must be a valid ID from a previous spawn, but the context is reasonable. The description adds minimal extra meaning beyond the schema's property name.

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 clearly states the tool's action ('Cleanly ends a presence'), the resource it applies to ('created by spawnPresence'), and its role in a sequence ('step 3 of 3'). It does not explicitly distinguish from siblings like retireArtifact, but the context of presence is specific enough to avoid confusion.

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 provides an explicit 'when to use' directive: 'Always call this when the presence is no longer needed.' It also explains the rationale — 'concurrent live presences are capped' — signaling that cleanup is important. However, it does not describe when NOT to use it (e.g., if the presence is already ended) or alternatives.

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