メモを追加

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

No annotations are provided, so the description must disclose behavior. It only reveals that login is required and that a new memo is added; it does not mention persistence, return values, side effects, duplication behavior, or errors. This is thin for a mutation 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?

The description is a single concise sentence that conveys both the purpose and the authentication prerequisite. There is no filler or redundant content.

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 simple two-parameter creation tool with fully documented schema, the description covers the essential purpose and the auth requirement. The lack of output schema and response details is not critical here, though mentioning the result of the operation would make it fully complete.

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 100% and both parameters already have clear descriptions. The description's mention of 'text' adds little beyond the string type, and 'login required' is already implied by the token parameter. It meets the baseline but adds no real parameter-level insight.

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 clearly states the action 'add' and the target resource 'new memo', plus the format 'as text'. It is easily distinguished from sibling tools like list_memos, delete_memo, register, and login.

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 explicitly notes that login is required, giving a clear prerequisite for use. It does not name alternatives or exclusions, but the add-vs-list/delete distinction is obvious enough from the sibling names.

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