create_rom_note

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

Annotations already indicate a non-read-only, non-idempotent mutation, but the description adds no behavioral context beyond the word 'Create'. It does not describe side effects, authorization needs, or how optional fields like content, tags, and is_public behave.

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 sentence with no redundant phrases, and it front-loads the action and resource. The phrase 'with explicit supported fields' is somewhat uninformative, but overall the text is concise and easy to parse.

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 5-parameter creation tool with 0% schema description coverage, this description is far from complete. The output schema reduces the need to describe return values, but the parameter semantics and usage context are still missing, making correct invocation uncertain.

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 does not compensate by explaining any parameters. 'Explicit supported fields' is unhelpful because it names no fields. An agent is left to infer the meaning and relationship of rom_id, title, content, tags, and is_public entirely from names and defaults.

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 specifies the verb 'Create' and the resource 'RomM note', which distinguishes it from siblings like update_rom_note, delete_rom_note, and list_rom_notes. However, the phrase 'with explicit supported fields' is vague and does not enumerate what those fields are.

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 provides no guidance about when to use this tool versus updating, deleting, or listing notes. It also does not mention prerequisites, such as needing a valid rom_id or that this tool is for creating new notes only.

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