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

Annotations already indicate this is a write operation (readOnlyHint=false) and non-idempotent. The description adds behavioral context beyond annotations by requiring the skill_id to be the exact endorsement ID from linkedin_skills and forbidding skill-name input, which is critical for correct invocation. It does not disclose side effects or failure modes, but the workflow constraint is a meaningful addition.

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 two sentences with zero filler. The core action is stated first, followed by the two critical procedural constraints. Every clause adds necessary information; there is no redundant or vague wording.

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 no output schema, the description provides the essential preconditions, the source of each required ID, and the primary pitfall to avoid. It could explain what happens if the skill_id is invalid or if the member is not a relation, but the current guidance is sufficient for correct invocation in the common case.

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 input schema already provides 100% coverage with detailed parameter descriptions, so the baseline is 3. The description adds value by prescribing the order of operations: member_id must be resolved first)SkipLinkedIn_profile via linkedin_skills, and the returned endorsement skill_id must be reused exactly. It reinforces the most important semantic rule (never pass a skill name) and explains the provenance of both required parameters.

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 a specific verb and resource: 'Endorse one skill on a LinkedIn relation.' It also distinguishes the action from related profile operations by specifying the endorsement skill context, and states the required workflow (resolve member_id, fetch profile, reuse skill_id), leaving no ambiguity about what the tool does.

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 clear procedural context: resolve member_id first, fetch the profile with linkedin_skills, and reuse the exact returned endorsement skill_id, plus a hard constraint to never pass a skill name. It does not explicitly name an alternative tool or state when not to use it, but the workflow is specific enough for an agent to know exactly when and how to invoke it.

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