linkedin_add_award

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

The description adds no behavioral information beyond what annotations already convey (readOnlyHint=false implies mutation). It does not disclose possible side effects, authentication requirements, idempotency (or lack thereof), or consequences of repeated calls. Since annotations are present, the description contributes no extra transparency.

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 very short and front-loaded with the verb, making it easy to scan. However, 'honour or award' is somewhat redundant since an award is a type of honour; simplifying to 'award' would be more concise, but overall it is not verbose.

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 simple write tool with a well-described schema, this is minimally viable but lacks important context such as return value or whether the operation appends or replaces existing awards. The absence of an output schema means the description could have disclosed result expectations, but it does not. Annotations and schema partially compensate, so it is not incomplete enough for a 2.

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 already describes 4 of 5 parameters with meaningful details (e.g., startMonth accepts both name and number), so baseline is 3. The description adds no parameter-specific meaning and does not clarify relationships between parameters; it merely repeats the tool's purpose.

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 states a specific verb ('Add') and resource ('honour or award') and specifies the target ('the profile'), making the tool's function unambiguous. This clearly differentiates it from sibling tools like add_certification or add_skill, as it unambiguously targets awards/honours.

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?

No guidance is provided on when to use this tool versus the many alternative 'add_*' siblings, nor are any exclusions or prerequisites mentioned. The description is purely an action statement without contextual cues about appropriate use cases.

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