create_reaction

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

With no annotations provided, the description carries full burden and does well by disclosing: the API requirement, what gets created (reaction details returned), and behavioral notes about deprecated reaction types. It doesn't mention rate limits, authentication specifics, or error conditions, but provides substantial operational context.

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?

Well-structured with purpose statement, prerequisite, parameter documentation, return information, and important note. Every sentence earns its place, though the reaction options list is somewhat lengthy but necessary. Could be slightly more front-loaded with the core purpose.

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?

Given the tool's moderate complexity (2 parameters, mutation operation), no annotations, but with output schema present, the description is remarkably complete. It covers purpose, prerequisites, parameter details, return information, and important behavioral notes about deprecated functionality - providing everything needed for effective use.

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 0% schema description coverage, the description fully compensates by providing detailed parameter semantics: explains what target_urn represents with concrete examples, documents all reaction_type options with their display equivalents, and specifies the default value. This adds significant value beyond the bare schema.

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 specific action ('Add a reaction') and target resource ('to a LinkedIn post or comment') using the verb+resource pattern. It distinguishes this tool from sibling tools like 'create_comment' or 'delete_reaction' by focusing specifically on reaction creation.

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 clear context about when to use this tool (for adding reactions to LinkedIn content) and includes an important prerequisite ('Requires "Community Management API" product enabled'). However, it doesn't explicitly contrast when to use this versus alternatives like 'delete_reaction' or other engagement tools.

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