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

Annotations only say readOnlyHint=false and destructiveHint=false; the description adds real context beyond that: the write lands in a 'recommended' pending state and is never used or shown to members until a steward approves, so the agent knows the effect is deferred and non-public. 'Terms are plain text, never a person' also discloses a value constraint. It does not cover what happens on rejection or whether duplicates are merged.

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 sentences, no padding, and the core action is front-loaded before the approval caveat. Slightly elliptical phrasing ('It lands as recommended') costs a little clarity but no words are wasted.

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?

A write tool with no output schema and five parameters lacking schema descriptions needs more: the description covers the approval lifecycle but omits parameter roles, duplicate/idempotency behavior, and what an agent gets back (e.g., a pending declaration id). Adequate to understand intent, insufficient to invoke reliably.

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 carries the full burden, yet it never mentions the parameters. It partially explains 'relation' values (already in the enum) and says terms are plain text rather than persons, but gives no meaning for 'subject', 'object', 'label', or 'token' — the distinction between label and token is especially opaque.

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: declare how interests relate, naming the relation vocabulary (serves, kind-of, part-of, alias-of). An agent can tell this is about asserting semantic relations between entities, though 'interests' is used loosely relative to the tool name's 'affiliations' framing, leaving mild ambiguity about the domain.

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?

There is no explicit statement of when to use this versus alternatives (no siblings are named, and propose_type / knowledge_lens are plausible confusions). The only guidance is implicit in the approval-workflow sentence, which hints this is the proposal step rather than the confirm step.

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