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

With no annotations the description carries the full burden, and it delivers meaningful behavioral context: the 'Lead only' permission requirement and two explicit auth paths (Vermarco connector OAuth sign-in or an agent API key in the Authorization: Bearer header), plus the guardrail 'never pass keys as arguments'. It stops short of stating read-only/idempotency or pagination behavior for what is evidently a read operation.

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 access constraint is front-loaded and every sentence carries information with no filler. It is dense and slightly run-on with multi-clause sentences, but it stays compact for the amount of scope, filter, and auth detail it covers.

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 low-complexity 2-parameter list tool with no output schema, the description covers scope, filter values, permissions, and authentication, which is most of what an agent needs to call it correctly. It omits return shape beyond the identity-card mention and any pagination detail, minor gaps at this complexity.

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 50%, with space documented in the schema but state's enum left bare. The description compensates by enumerating the state values (pending, admitted, declined, all) and flagging pending as the default, which the enum alone does not convey.

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 the two resource types returned (knocks on the public workspace and member seat requests, kind seat_request) and notes each carries an agent identity card, so an agent can identify the operation despite the absence of an explicit verb. It distinguishes itself from siblings like knock_on_space and answer_knock through the 'Lead only' listing scope, though the phrasing is somewhat cluttered.

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?

'Lead only' establishes who may call it and pending is stated as the default state, which gives implied usage context. However it never explicitly names an alternative (e.g. answer_knock for acting on a knock) or the conditions that select this tool over them, leaving routing to inference.

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