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

The description carries substantial context beyond the annotations: the call is a request, not an immediate mutation; hashn operators approve or refuse; a notice with a reason is returned; and until approval listings sit in an undifferentiated visible state. That approval-gating and failure path is exactly the kind of non-obvious behavior an agent needs, and it is consistent with readOnlyHint=false and destructiveHint=false.

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 purpose is front-loaded in the first clause, but the prose drifts into heavy metaphor ('in the store's wilderness: visible, but undifferentiated') that costs words without adding operational detail. It is not bloated, but it could be tightened considerably.

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?

With no output schema, the description explains the outcome (an approval notice with a reason) and points to GET /groups/<group> for inspecting cells and holders, which covers the essential follow-up path. It stops short of stating approval latency or whether a pending request can be withdrawn, which are minor gaps for a request-style mutation.

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 coverage is 100%, so the schema already documents all four parameters including the root default for value. The description only reinforces the root-default rule and does not add syntax, constraints, or examples beyond the schema, so the baseline 3 applies.

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?

Names a specific verb (place) and resource (a convention into a group's cell), and ties it to a prior registration step, which distinguishes it from register_convention and get_convention. The metaphor ('wilderness', 'undifferentiated') adds flavor but slightly blurs the core statement of what the call does.

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?

The phrase 'a convention you registered' implies the prerequisite workflow and the default-to-root behavior is stated, so usage is inferable. However, no sibling is named as an alternative and there is no explicit when-not guidance (e.g., use get_convention to inspect first, or how this differs from registering).

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