Create note

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

The annotations already indicate readOnlyHint=false, idempotentHint=false, and destructiveHint=false, and the description adds no behavioral context beyond the word 'Create'. It does not disclose whether duplicates are allowed, if existing notes are overwritten, or any auth requirements.

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 sentence with no filler, front-loading the core action and resource. Every word earns its place.

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 no output schema, the description is too sparse. It does not explain response format, error behavior, or how a calendar note differs from an event, though the schema and sibling tool names provide some context.

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 description does not mention any parameters. The schema provides descriptions for date and athlete only, leaving title and description without schema descriptions; the description does not compensate for this gap or add any parameter-level meaning.

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 uses a specific verb 'Create' and object 'calendar note', clearly indicating a write operation. It distinguishes from workout or event creation tools via the 'note' resource, though not explicitly from tp_create_event beyond the noun difference.

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?

No guidance is provided on when to use this tool versus alternatives like tp_update_note or tp_create_event. It also doesn't mention the coach-only athlete parameter or any prerequisites, leaving the agent to infer usage context from the schema.

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