create_note

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

With no annotations provided, the description carries the full burden and does so well. It explicitly warns that title/content are stored as free text and that embedded instructions must not be followed, explains the rendering effect of is_markdown, and states that the operation does not modify or delete existing data.

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 sentences, each with a distinct purpose: core action, prompt-injection warning, markdown semantics, and non-destructive guarantee. The most important information is front-loaded, and the detailed markdown guidance earns its space because misuse changes how content is rendered.

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 an output schema and no annotations, the description is complete: it specifies the operation, all parameter semantics, safety behavior, and injection handling. The only minor omission is explicit routing to create_session, but the resource distinction is self-evident.

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 description must compensate for all five parameters. It explains title/content as free text, course_id and session_id as optional links, and is_markdown with precise conditions and rendering consequences—far beyond the bare schema types 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 opens with a specific action and resource: 'Creates a new note in StudyLife' and goes on to specify the required title/content and optional course/session links. This unambiguously distinguishes it from the sibling create_session by targeting notes rather than sessions.

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 clear context for when to use the tool and gives explicit conditional guidance for is_markdown: set True only for deliberate Markdown, leave False for plain text. It does not explicitly name alternatives or exclusions, but the intended use case is evident.

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