update_note

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

With no annotations, description carries full burden. Discloses operation (add/update upsert), max note length (500 chars), and domain must be favorite. Could mention idempotency or side effects more explicitly, but sufficient.

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?

Concise two-paragraph structure: purpose, usage guidance, then args list. Each sentence adds value, but could be slightly tighter (e.g., 'Args:' redundant if using structured format).

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?

Covers inputs, usage constraints, and when to use. Lacks return value description (no output schema), but acceptable for a mutation tool. Overall complete for its complexity.

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 coverage is 0%, so description adds meaning for all three parameters: source of project_id (list_projects), condition for domain_id (must be favorite), constraint for note (max 500 characters). Fully compensates for missing schema descriptions.

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?

Clearly states verb-resource: 'Add or update a note on a favorite domain.' Distinguishes from siblings like add_favorite and project_favorites by focusing on notes specifically.

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?

Explicitly says when to use: 'Reserve notes for standout opportunities... Do NOT annotate every domain.' Also notes prerequisite: domain must be a favorite. Lacks direct comparison to alternative tools but provides clear context.

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