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

No annotations are provided, so the description must carry all behavioral disclosure. 'Requires authentication' is a useful safety signal, but the description omits any information about side effects (e.g., whether it overwrites existing experiences), response behavior, or potential errors. For a mutation tool, this is insufficient.

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 – one sentence with no redundancy. However, it is under-specified for an agent to use effectively. While it earns credit for brevity, it loses points for lacking essential context that could have been included without bloat.

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 tool with 9 parameters, 4 required, no output schema, and no annotations, the description is too minimal. It does not mention the required fields, the format of dates, the existence of the experience_skill_list parameter, or any success/error behavior. An agent would need to deeply inspect the schema to understand all constraints, but even then, behavioral expectations are unclear.

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% – every parameter has a description in the schema. The tool description adds no additional parameter meaning beyond the schema. Per the guidelines, baseline 3 is appropriate when the schema fully documents parameters, and the description neither helps nor hurts.

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 work experience to your Himalayas profile.' It identifies the specific resource (work experience) and destination (profile). It is distinct from sibling add_education, though it doesn't explicitly contrast them. The verb 'Add' is specific and unambiguous.

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 no guidance on when to use this tool versus alternatives like add_education or update_profile. It only mentions authentication, which is a requirement, not a usage condition. The intended use case is implied by the name, but not explicitly stated.

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