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

With no annotations, the description carries full load. It usefully discloses partial-update semantics and the empty-string-clears-prompt behavior, but omits permission requirements (owner/admin) and error behavior for a mutation tool; it also repeats the 'omit to leave unchanged' rule already present in every schema property.

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 tight sentences, front-loaded with the action and fields, then the patch rule, then the edge case. Nothing is padded and each sentence earns its place.

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 output schema and fully documented parameters, the description covers the essentials: what changes, patch semantics, and prompt clearing. It would be complete with a note on permissions (visibility is owner/admin only), which it omits.

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 the baseline is 3. The description adds the AGENTS.md location and clearing semantics for prompt, but says nothing about visibility, which the schema alone documents; value beyond the schema is marginal.

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 (edit) and resource (board metadata: title, code) plus the board-level agent prompt, so an agent knows this mutates board attributes. It does not explicitly distinguish itself from the sibling set_board_setting or get_board_prompt, leaving sibling routing to inference.

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 patch semantics ('pass only the fields you want to change; omitted fields are left untouched') is good operational guidance, but there is no explicit when-to-use versus alternatives like set_board_setting, nor any stated preconditions. Usage is implied rather than framed.

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