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

The description adds meaningful behavioral context beyond the annotations: it states the operation is 'deterministically validates the payload and atomically creates a private profile when needed or replaces the owner's profile facts and complete experience list,' which aligns with the destructive and idempotent hints. It also discloses that 'person.work does not run a second AI interpretation' and that logos are 'imported a protected copy.' These details go beyond what annotations alone convey.

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 a single paragraph of about six sentences, each contributing a distinct point: the operation type, exclusions, validation behavior, logo handling, identity requirement, and usage caution. It front-loads the primary purpose and uses clear, direct language. There is minimal redundancy, though it could be tightened slightly without losing information.

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 complex operation with nested objects, no output schema, and annotations that are not self-explanatory, the description covers the essential aspects: what it does, what it rejects, creation vs. replacement, logo handling, identity conditions, and a strong usage warning. It does not describe the response format or error scenarios, but given the operation's nature and the absence of an output schema, the provided context is sufficient for an agent to invoke it correctly.

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?

The schema has 50% description coverage, and the description adds value for some key parameters: it explains the null-vs-omit semantics for company_logo_url and avatar_url, and clarifies that identity is only for first creation. However, it does not elaborate on many other fields (e.g., competencies, extension fields), which are left to the schema. Since coverage is moderate, the description partially compensates but not exhaustively.

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 'Explicit initial-import operation for structured facts already interpreted by the calling agent,' which precisely states the verb (import), the resource (structured CV facts), and the scope (initial import only). It also explicitly negates what it does not do ('does not accept or store a raw CV, PDF, or source text'), and the title reinforces the action. This clearly distinguishes it from sibling get and propose tools.

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 gives explicit usage guidance: 'Never use this for routine updates' tells the agent when not to use it, and 'Identity is required only for first creation' sets a condition. It implies this is for initial import rather than updates, which differentiates it from propose_my_career_change, though it does not name the alternative explicitly. The 'initial-import operation' label provides clear context.

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