append_note

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

With no annotations, the description carries the full burden and partially delivers: it discloses the append (non-overwrite) semantics, the timestamping, the agent-name tag, and the target file. It omits whether the file is created if missing, where StoneWay.md lives, and any permissions/error behavior, so gaps remain for a write tool.

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?

One sentence with the action front-loaded and no redundant restatement. 'Quickly' is mild marketing filler but arguably conveys lightweight intent, so the sentence largely 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?

An output schema exists, so return values need not be explained, and the two-parameter surface is simple. However, a write tool with no annotations and an unspecified file location/creation policy leaves the agent without enough context to predict side effects.

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 must compensate. It explains that 'note' holds a scratchpad note/idea/observation and that agent_name is used as a tag, which covers both parameters semantically, but gives no format expectations or mention of the nullable default the schema declares.

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 ('appends a timestamped scratchpad note... into StoneWay.md') and adds scope details (timestamped, tagged with agent name). The sibling tools are all profile/sync oriented, so no confusion arises; an agent can tell this is the note-capture tool immediately.

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 'scratchpad note, idea, or observation' implies the intended use case, but there is no explicit when-to-use/when-not guidance or comparison to an alternative capture mechanism. For a sibling set with no competing note tool, implied usage is adequate but not strong.

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