Create a new Markdown note in Fastidious using a title and content, with optional custom fields or a parent collection for organization.
Create a new note in Fastidious. Notes should be in Markdown format.
| Name | Required | Description | Default |
|---|---|---|---|
| title | Yes | Title of the note | |
| fields | No | Optional: Custom fields as key-value pairs | |
| content | Yes | Content of the note in Markdown format | |
| parentId | No | Optional: ID of parent collection to add this note to |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the Markdown format requirement but omits permissions, side effects, whether the note is returned, and any rate limits or reversibility concerns for this write operation.
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?
Two short sentences with no wasted words; the core purpose is front-loaded, and the format constraint follows naturally.
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?
Given the simple create operation and full schema coverage, the description covers the essential purpose and format. However, without annotations or an output schema, it lacks behavioral details such as what the tool returns or whether authentication is required.
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 100%, so the schema already documents all four parameters. The description's note about Markdown format reinforces the content parameter but adds no meaning beyond what the schema provides.
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 specific verb ('Create') and resource ('note'), making the operation clear. However, it does not differentiate itself from sibling tools like update_note or create_collection beyond what the tool name already conveys.
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?
There is no guidance on when to use this tool versus alternatives such as update_note or create_collection. The description only states the operation, leaving context entirely to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.