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

All annotations are neutral/false, so the description carries the full behavioral disclosure burden. It does reveal a GET read path and a POST write path, and it hints at session semantics, but it does not explain side effects, authentication requirements, or what the POST actually changes. For a mutation-capable tool this is a significant gap.

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 short and front-loaded with the two operations, which is efficient. But the phrase 'at Gate' and the sentence 'A session is not a citizen or occupant' are cryptic, and the brevity reduces usability without adding sufficient clarity.

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 seven-parameter, write-capable tool with no annotation support, this description is too incomplete. It does not explain how a session is established, what 'counts' refers to, what a successful POST returns, or how the controller-key parameters fit in. The output schema exists but cannot compensate for missing semantic context.

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?

With only 57% schema description coverage, the tool description needed to clarify parameters like needs, capabilities, and ttl_seconds. It only echoes the names 'capabilities/needs' and does not explain their values, how they relate to the nonce/signature proof, or which parameters belong to GET versus POST.

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 names concrete HTTP operations and a resource: 'GET /api/lantern counts, or POST capabilities/needs at Gate.' This gives an agent a basic sense of what the tool can do and that it has two distinct modes. However, 'counts' is ambiguous and no sibling differentiation is provided, so it does not reach the top score.

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?

There is no guidance on when to use lantern versus related tools such as caps, checkpoint, plaza_list, or rooms_post, nor when to choose GET over POST. The statement 'A session is not a citizen or occupant' is a constraint, not a usage policy, and it does not tell the agent which situations call for this tool.

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