create_concept_note

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

The description discloses the core behavior: writing one atomic concept note and linking into the graph. However, no annotations are provided, and the description does not mention what happens when overwrite is true, whether an existing note is replaced, or what the tool returns. Given the overwrite parameter, this is a meaningful transparency gap.

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 four short, front-loaded sentences with no filler. Every line earns its place by explaining what the note should contain and how to prepare links.

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 create tool with 7 parameters, no annotations, and no output schema, the description covers the core workflow well but omits overwrite behavior and optional field semantics. It is adequate for basic use but not fully complete for safe handling of the overwrite case.

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 prose must carry parameter meaning; it does for title, claim, and links with unusually specific semantics. However, body, tags, sources, and especially overwrite are left unexplained, so it only partially compensates for the complete lack of schema 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?

The description states a specific verb and resource: 'Write one atomic note: one idea, stated as a claim.' The title and claim guidance ('assertion you could disagree with, not a topic label') clearly differentiates this from generic create_note and other note-related siblings.

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?

It gives clear procedural guidance: links must be titles of existing notes, so the agent should call find_notes or search_notes first to avoid creating an island. It does not explicitly say when to prefer this tool over create_note or append_to_note, but the intended use case is strongly implied.

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