Create notes

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

With only openWorldHint annotation, the description carries the transparency burden but only says what the tool does, not how it behaves (e.g., whether it validates, overwrites, or returns a result). It also contains a parameter-name mismatch (entity_id vs entity_type) that could mislead. No side effects or permissions are disclosed.

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 very brief (two sentences) and front-loaded with the key requirement. However, the repetition of 'Create notes' from the title is unnecessary, and the conciseness sacrifices critical clarity about the schema.

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 tool with two required parameters, no output schema, and no parameter descriptions, the description should fully compensate. It does not: it omits the entity_type enum, leaves the notes array structure opaque, and includes a conflicting 'entity_id' reference. The tool is underspecified for correct invocation.

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. It mentions entity_id, note_type, and params, but the schema uses entity_type and a notes array. It gives a partial example ({ text }) but fails to explain the notes array structure or the allowed entity_type values, and the entity_id reference is misleading.

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 clear verb ('Create') and resource ('notes'), distinguishing it from sibling list/get/update/pin/unpin tools. However, it introduces confusion by mentioning 'entity_id' while the schema uses 'entity_type', and the title is near-tautological with the first sentence.

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?

Usage is implied by the name and description: this is the creation tool for notes. There is no explicit contrast with alternatives like update or list, nor when/not to use it. The description only hints at required data, not context or exclusions.

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