he_add_favorite

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

No annotations are provided, so the description carries the full burden. It adds the important behavioral note 'ask user confirmation', but does not disclose other behaviors such as duplicate handling, permissions, side effects, or success/error responses.

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 extremely concise: two short sentences. The first sentence states the purpose, and the second adds a critical behavioral instruction. No unnecessary words, and the important note is front-loaded.

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 add-to-favorites tool with only two parameters and no output schema, the description covers the core action and a key behavioral requirement. However, it could be more complete by mentioning what happens on success or any prerequisites (e.g., user must be authenticated).

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 100% with descriptions already provided for both parameters. The tool description merely echoes the schema descriptions ('Property ID to add' and 'Optional wishlist folder ID') without adding new meaning or constraints.

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 clearly states the action 'Add a property to favorites' with a specific verb and resource. It also mentions optional wishlist folder specification, adding precision. The sibling tools include he_remove_favorite and he_get_favorites, so this tool's purpose is distinct and easily understood.

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 provides the use case ('Add a property to favorites') but does not compare this tool to alternatives like he_remove_favorite or he_get_favorites. The 'IMPORTANT: ask user confirmation' is a behavioral guideline but not about when to use the tool versus others.

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