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

No annotations are provided, so the description carries the full burden, and it does disclose real side-effect behavior: templateId 0 unbinds, and without a matching rule the slot falls back to the archive record's own blocks and is empty only where no record exists. It omits permissions/auth and reversibility, but the fallback semantics are genuinely useful.

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?

Front-loads the core action, then the context enumeration, then the fallback and rules. It is dense and the parenthetical is heavy, but each clause carries operational information rather than filler.

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?

An output schema exists, so return values need not be explained. For a two-param binding tool the description covers the format, the unbind convention, the fallback behavior, and the prerequisite doc; only permission/error behavior is left unstated, which is a minor gap.

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 fully documented in the schema, including the 0-unbind convention and the context format. The description mostly restates those values; its only added value is pointing at list-archives as the source of the context value. Baseline 3 is appropriate.

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 and resource: 'Bind a site template to an archive view.' This is clearly separable from the sibling fabrement-assign-template-pages (archive views vs. pages), so an agent can route correctly without opening the schema.

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?

Gives concrete when-to-use context: the template's contentSource 'wants a rule for the same context (save-archive-page + save-template)', and explicitly directs reading the template-contract skill doc before the first call. It does not, however, explicitly contrast with the sibling assign-template-pages, so the alternative is only implicitly distinguished.

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