Add project note

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

Annotations already establish mutation and open-world behavior, while the description adds concrete visibility ('company's users with access'), notification behavior ('Nobody is notified'), actor ('signed-in user'), and return value ('saved note'). It omits permission scopes and duplicate/rate-limit behavior, so it is strong but not exhaustive.

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 front-loaded and generally concise. The first sentence largely duplicates the second ('Adds a note...' / 'Writes a note...'), which is a minor redundancy.

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 simple mutation tool with annotations but no output schema, the description covers purpose, visibility, notification, actor, and return value. Missing duplicate handling or edit restrictions are modest gaps.

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 33%; only project_id has a schema description. The prose mentions an optional title but does not explain text body semantics or limits, and does not compensate for the low schema coverage.

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 and resource: 'Adds a note to a project's Notes tab.' The write operation is unmistakable, though it does not explicitly name the read sibling list_project_notes, so sibling differentiation is implicit rather than stated.

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 explicit when-to-use, when-not-to-use, or alternative tools are named. Visibility and notification details describe behavior, but they do not route the agent between add_project_note and list_project_notes or other note-related actions.

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