Create memo

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), and the description adds genuinely useful behavior: visibility default resolution (preference, usually PRIVATE, vs SPACE when placed in a space), inline tag handling, and that local attachment files get uploaded. It stops short of stating auth requirements or what happens on failure.

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?

Four compact sentences, front-loaded with the core action, then conditional details (tags, task lists, visibility, attachments). Dense but each sentence carries actionable information with no filler.

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 an 8-parameter mutation tool with only 1 required parameter, 88% schema coverage, and no output schema, the description supplies the defaulting rules that an agent could not infer from the schema alone. Remaining gaps (auth, error behavior) are minor given the annotation coverage.

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 already 88%, so the baseline would be 3, but the description adds semantics the schema does not: tags are appended as #tag only if not already present, and local file paths in attachments are uploaded and attached. That is meaningful clarification beyond the property descriptions.

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 ('Create a new memo') plus the input format ('from Markdown'), which immediately separates it from update_memo, edit_memo_content, and the read siblings. An agent knows exactly what this tool produces without opening the schema.

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 description implies usage through behavioral defaults (visibility falls back to preference, space placement changes visibility) but never states when to choose this over update_memo or edit_memo_content, nor any prerequisites. Context is implied rather than given.

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