Add project to portfolio

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

With no annotations, the description carries full burden. It discloses the key behavioral trait that adding an already present item moves it to the specified position. However, it does not mention permissions, error handling, idempotency nuances, or response behavior, leaving some gaps.

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?

Two sentences with no wasted words. The first sentence states the core action and optionality, the second adds the critical duplicate behavior. Each sentence 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?

Given no output schema or annotations, the description adequately covers the main operation and the duplicate scenario. It could be more thorough about success/failure responses or prerequisites, but the 100% schema coverage compensates partially.

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 100%, so baseline is 3. The description adds no significant parameter detail beyond the schema; it only implies the optional positioning but does not elaborate on format or constraints of insert_after/insert_before.

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 'Add' and identifies the resource as 'a project (or sub-portfolio) to a portfolio'. It also clarifies the optional positioning and the duplicate behavior, which distinguishes it from sibling tools like portfolio_remove_item and portfolio_list_items.

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 clearly states the tool's function (adding items to a portfolio) and implicitly distinguishes it from siblings by focusing on addition. However, it does not explicitly provide when-to-use or when-not-to guidance or name alternatives.

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