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

Annotations already establish this is a non-read-only, non-destructive, closed-world mutation, and the description usefully adds that 'everyone' is the default and that the setting scopes only direct knocks, not public-workspace knocks. That scope boundary is genuine context beyond the annotations. It omits anything about auth or reversibility, though the api_token parameter covers auth.

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?

Two sentences, front-loaded with the setting's meaning, then the scope caveat and the read alternative. No filler, though the second sentence mixes scope and read-guidance somewhat loosely.

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 two-value settings mutation with no output schema and full schema coverage, the description supplies the value meanings, the default, the scope boundary, and a way to inspect the current setting. Nothing essential to invoking it correctly is missing.

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 both parameters are already documented in the schema. The description restates the two values of direct_knocks and their meanings, adding little beyond the schema and nothing about api_token. Baseline 3 applies when the schema carries the parameter burden.

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 states the resource and what is being configured ('who may knock on you directly') and enumerates the two allowed values with their meanings, so the effect of calling it is clear. It never uses an explicit verb like 'sets', reading more like a parameter explanation than a purpose statement, and it does not distinguish itself from siblings like knock or list_knocks.

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 implies the usage context by noting the default ('everyone') and that public-workspace knocks are unaffected, and it points to whoami for reading the current value. However, it gives no explicit when-to-use or when-not-to-use guidance and does not name an alternative for changing this setting.

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