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

With annotations all false, the description adds critical behavioral context: upsert semantics, required fields on create, partial-only updates, and a precondition to check get_profile. It also includes an anti-hallucination instruction ('don't fabricate or embellish'), which is beyond the 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?

The description is informative without being bloated. The first sentence captures core behavior, the second provides strategic guidance, and the third gives a safety instruction. Each sentence adds value, though the motivational sentence could be considered slightly extraneous for tool invocation.

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 13-parameter tool with no output schema, the description covers the essential operational details: upsert behavior, required fields, partial update, and duplicate avoidance. It could mention response format or error cases, but those are less critical given the schema's full parameter coverage.

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%, so baseline is 3. The description adds meaning beyond the schema by clarifying that title and shortDescription are required for create (though the schema lists them as optional), and that updates only change passed fields. This is significant for correct invocation.

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 a specific verb and resource ('Add or update a portfolio project (upsert)') and distinguishes create from update behavior with explicit references to id and get_profile. This clearly differentiates it from sibling tools like save_work_experience or update_profile.

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?

It provides explicit usage context: omit id to create, pass id from get_profile to update, and check get_profile first to avoid duplicates. It does not name alternative tools explicitly or state when not to use it, but the create/update distinction and prerequisite are clear.

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