create_note

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states that lines are 'stacked downwards from position' and that the result is one 'Note' block, which gives some layout behavior. However, it does not disclose what happens with alignment, scale, layer, or height defaults, whether the note is editable later, or what the output schema contains. For a creation tool with no annotations, this is a significant 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 a single concise sentence that front-loads the core concept (multi-line note) and the key behavior (stacked downwards from position). It earns its place without fluff, though it could add a bit more detail without becoming verbose.

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 tool has 6 parameters, no annotations, and no schema descriptions, the description is not complete enough. It explains the basic layout behavior but omits the meaning of align, layer, scale, and height, and does not mention what the output schema contains. An agent would need to infer or guess the semantics of most parameters.

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 the undocumented parameters. The description only explains the 'lines' and 'position' parameters implicitly ('lines stacked downwards from position'), but it does not explain 'align', 'layer', 'scale', or 'height'. With 6 parameters and zero schema descriptions, the description leaves most parameter semantics unexplained.

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' block), and clarifies that it is a multi-line note with lines stacked downwards from a position. It distinguishes itself from sibling tools like create_text and create_room_label by emphasizing the multi-line 'Note' block concept, though it doesn't explicitly name those alternatives.

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 implies usage context: it is for creating a multi-line note block at a position, which is a distinct use case from other creation tools. However, it does not explicitly state when to use this tool versus alternatives like create_text or create_room_label, nor does it mention any exclusions or prerequisites.

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