linkedin_add_honor

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

The description only states the action without disclosing behavioral traits such as whether the operation is idempotent, what happens on duplicate entries, or if authentication is required. No annotations are provided to supplement, leaving significant gaps in 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 a single, concise sentence that efficiently communicates the basic purpose. However, it is too brief given the tool's 5 parameters, missing opportunities to add useful structure without sacrificing conciseness.

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?

The description fails to provide adequate context for the tool's usage. No output schema, annotations, or details about success/error behavior are given. The agent would struggle to understand the full implications of invoking this tool.

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?

With only 40% schema description coverage, the description adds no additional meaning beyond the schema. Parameters like 'year' and 'month' are left unexplained, and the 'description' parameter lacks any context. The description does not compensate for the schema's incompleteness.

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') and the resource ('honor or award to the LinkedIn profile'), making the tool's purpose unambiguous. It is easily distinguished from sibling tools like 'linkedin_add_experience' or 'linkedin_add_education' which target different profile sections.

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 alternatives, nor are any prerequisites (e.g., requiring a LinkedIn login) mentioned. The description lacks context for proper selection among the many sibling add tools.

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