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

With no annotations, the description carries the full burden and does meaningful work: it discloses blast radius ('shown to EVERY account at handshake'), permission model (platform admins only, immutable by orgs), and the high-stakes semantics of a divergent result (DB silently overrides code so code changes reach nobody). It does not state what `set` returns or whether it overwrites silently outside the drift concept.

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 text is front-loaded with what the block is and is dense with load-bearing detail rather than filler. However, it is a single run-on paragraph with nested parentheses and mixed backtick/bold formatting that is harder to parse than necessary.

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 four-parameter, multi-operation admin tool with no output schema and no annotations, the description covers mutation risk and drift semantics well. It leaves gaps on return values for list/get, the meaning of `_org`, and confirmation behavior for set, which an agent would need.

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 0%, so the description must compensate. It documents op values, the single valid key ('secret_sauce') and that body_md is the markdown body, but `_org` is never mentioned and body_md's format is only hinted at by its name. Coverage of three of four parameters is adequate but incomplete.

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 a specific resource (the platform-level injected instruction block #50) and enumerates its four operations (list/get/set/drift). It distinguishes scope implicitly by stating it is 'editable only by platform admins, immutable by orgs', which separates it from org-level guide tools, though it never names a sibling alternative explicitly.

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?

Each op is given a short usage gloss: list/get take a key, set takes key plus body_md, and drift takes no argument and compares DB-served prose against code-carried prose. The 'editable only by platform admins' clause communicates a prerequisite. It stops short of explicit when-not-to-use guidance or naming the guide/doctrine siblings an agent might confuse it with.

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