add_tracking_note

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

Annotations provide readonly=false (write operation) and destructive=false. Description adds context that it targets user_preferences.db and requires tracking enabled, which is useful behavioral info beyond 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?

Single sentence, no fluff. Essential information (verb, target, condition) is front-loaded and concise.

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 tool with well-documented schema and no output schema, the description provides purpose and condition. Slight gap: could mention behavior if tracking is disabled, but overall adequate.

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 has 100% coverage with descriptions for all 8 parameters. Description does not add additional meaning beyond the schema, so baseline score of 3 is appropriate.

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?

Clear verb 'Add' and resource 'tracking note to user_preferences.db' with condition 'only when tracking enabled'. Distinguishes from sibling 'add_note' by specifying tracking context.

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?

States condition 'only when tracking enabled', providing clear context for use. Does not explicitly mention when not to use or alternatives like 'add_note' for general notes.

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