create_notes

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

Annotations already indicate readOnlyHint=false (write operation), openWorldHint=true (potential side effects), idempotentHint=true, and destructiveHint=false. The description adds only the HTTP method and a pointer to read the schema. It does not disclose what happens on success, whether authentication is needed, rate limits, or any side effects beyond the annotation hints. The openWorldHint signals possible side effects, but the description does not elaborate, leaving the agent with little behavioral context beyond the annotations.

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 concise—two short sentences plus a parameter note. It front-loads the core action ('Add notes') and the HTTP method, and the parameter guidance is placed after. There is no wasted verbosity, and the structure is clear. However, it could be more informative without losing conciseness, hence a slight deduction from a perfect score.

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's complexity (openWorldHint, free-form body, nested objects) and that an output schema exists (though not shown), the description is sparse. It does not explain what a 'note' is, typical fields (e.g., text, timestamp, user), authentication requirements, or the expected response. The pointer to the schema is useful but does not provide immediate context. For a write tool with open-world semantics, this is insufficient for an agent to call it correctly without additional resources.

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?

The schema defines a single 'body' parameter as an object with additionalProperties: true, meaning it is free-form, and schema description coverage is 0%. The description tells the agent to 'Read the matching GET or the /schema endpoint first to see the fields this resource expects,' which compensates by pointing to where field definitions can be found. This adds value beyond the schema, but it does not enumerate any specific fields, so the agent still lacks direct knowledge of what to include.

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 'Add notes.' which is a clear verb and resource, and the HTTP method POST /notes further clarifies the action. It is unambiguous as a creation operation, especially given sibling tools like update_notes_by_id and delete_notes_by_id. However, it does not explicitly contrast with other create-like tools (e.g., create_comments) or mention the scope (user-specific? global?), so it lacks explicit sibling differentiation.

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 instructs 'Read the matching GET or the /schema endpoint first to see the fields this resource expects,' which provides a practical usage guideline for constructing the request. However, it offers no guidance on when to choose this tool over alternatives (e.g., update vs. create) or any exclusions. The usage context is implied but not explicitly contrasted with other note-related tools.

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