profile_add_item

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the key trait — this is an append (non-destructive to existing entries) rather than a replace — and adds a significant guardrail against fabricating user data. However, it says nothing about what happens on duplicate entries, invalid section names, or what the tool returns on success/failure.

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 core action is front-loaded in the first clause, followed by dense but useful per-section field specs, ending with a short guardrail. Every element earns its place. It reads as one run-on sentence with embedded brace notation, which is compact but slightly harder to parse than a structured list would be.

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 mutation tool with no annotations, no output schema, and a nested free-form object parameter, the description supplies the one thing the schema cannot: the expected item shape per section. What remains missing — exact section string matching, per-section required fields, and error/return behavior — are secondary for correct invocation but would be worth adding.

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 0% and the schema is a generic {section: string, item: object}, so the description does nearly all the work by enumerating the five valid sections and the field shape for each item type. That is meaningfully more than the schema provides. It loses a point because it never states that 'section' must match one of these exact strings (case/format), which fields are required per section, or whether bullets/tech are arrays of strings.

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 opens with a specific verb and resource: 'Append one entry to a list section.' Combined with the enumerated section list, an agent knows exactly what the tool does and can infer it is distinct from profile_update (whole-profile rewrite) and profile_remove_item (deletion). It stops short of explicitly naming those siblings, so it is not a 5.

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?

Usage is only implied by 'Append one entry to a list section' — the agent must infer that this is for incremental CV content addition rather than wholesale profile edits. There is no explicit 'use this instead of profile_update when...' routing, and no stated prerequisites. The closing rule 'Only add facts the user told you' is a data-integrity constraint, not when-to-use guidance.

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