Insert Zero Meeting Prep Note

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

Annotations already indicate this is a mutating, non-idempotent, non-destructive action, and the description's 'creation' is consistent with that. Beyond the annotations, the description adds only weak context ('manual', 'user-accessible') and does not explain effects, whether notes are appended or replaced, access requirements, or response behavior.

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 a single short sentence, which is structurally concise. However, the phrase 'OpenClaw-compatible' adds noise without contributing useful meaning, and the sentence is so terse that it sacrifices substance for brevity.

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 tool with two unnamed required parameters, no output schema, and several ambiguous sibling tools, this description is incomplete. An agent lacks enough information about parameter meaning, usage context, behavioral effects, and return value to confidently invoke it correctly.

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 burden of explaining meeting_id and note_text. It does not meaningfully explain either parameter beyond the obvious naming, nor does it mention constraints like note length or the need for the meeting to be accessible to the user.

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 states a verb ('creation') and a resource ('prep note for a user-accessible meeting'), so the basic action is identifiable. However, 'OpenClaw-compatible' is unexplained and the description does not distinguish this tool from the closely named sibling add_meeting_prep_note or replace_generated_prep_notes_for_meeting.

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 word 'manual' weakly implies use when a user is creating a note by hand rather than automatically generating one, and 'user-accessible meeting' hints at a permission condition. But the description gives no explicit when-to-use guidance, no exclusions, and no mention of alternative sibling tools, so an agent cannot reliably choose between this and add_meeting_prep_note.

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