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

With no annotations, the description carries the burden but does disclose a real behavioral trait: new rows are added with a normal 24h cooldown. It does not say what happens to existing or duplicate entries, whether applying requires governance approval or a second confirmation, or whether the operation is reversible.

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?

Three short, front-loaded clauses with no wasted words, and the agent-key routing is placed where it will be read. The telegraphic style ('GOVERN') costs a little clarity but keeps it tight.

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 mutation tool with no annotations, no output schema, and an undocumented parameter, the description covers the main effect and the key routing but omits the governance/approval flow, duplicate handling, and return behavior. Enough to choose the tool, not enough to call it confidently.

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?

There is one parameter with 0% schema description coverage, so the schema provides no help. The description implies the array is a list of allowlist recipients but never mentions the required address/chainId fields or the optional nickname, leaving the parameter largely unexplained.

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 a specific verb and resource ('Apply a validated recipient manifest') and constraints it to human/developer keys, which distinguishes it from the agent-key path. It is clear what the tool does, though the phrase 'apply' is not spelled out as creating allowlist entries until the second sentence.

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 gives an explicit alternative for the agent-key case ('use add_recipient per row (GOVERN)') and implies the human/developer scenario is the intended use here. It does not mention validate_recipient_manifest as the required prior step, even though the description says 'validated'.

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