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

With no annotations, the description usefully discloses that this is a mutation, that a Bearer token is required, and that notes are private. However, it does not explain whether notes replace or append to existing text, how notes are cleared or preserved, or whether stage transitions have restrictions.

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 description is compact and front-loads the tool's purpose before authentication and valid-stage details. Each part supports selection or invocation without unnecessary prose.

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?

Together with the schema, the description is sufficient for basic selection and invocation of this small three-parameter tool. Important gaps remain for a mutation with no annotations or output schema, particularly that stage is required even for a notes-only edit, how to preserve the current stage, and what the update returns.

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%, and the description only partially compensates by explaining the stage workflow and the privacy of notes. It merely repeats the stage enum already present in the schema, provides no explanation of saved_id, and omits useful notes semantics such as the 2000-character limit.

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 gives two specific operations on a saved-home board entry: moving it between stages and editing private notes. This clearly distinguishes it from board_save, which saves a home, and board_list, which retrieves entries.

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 stated operations provide clear when-to-use context: choose this tool to change an existing saved home's stage or notes. It does not explicitly exclude alternatives or explain that board_save should be used for initially saving a home.

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