linkedin_update_about

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

Annotations already signal readOnly=false and destructive=false, but the description adds valuable context that this is a full replacement operation. The warning to read existing profile first implies overwriting, which is behavioral context beyond what annotations provide. No contradiction with annotations.

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?

Three concise sentences. The first states the purpose, the second repeats a schema constraint, and the third gives a critical safety tip. No wasteful prose; it is front-loaded and efficient.

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 single-parameter mutable update tool with no output schema, the description covers all essential aspects: what is updated, scope (signed-in user), limits, and a safety precaution. It is complete enough for the agent to use it correctly.

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%, so the parameter (about) is fully described in the schema, including max length and line break preservation. The description only repeats the max character count and does not add new semantics beyond the 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 starts with 'Replace the About (summary) section on the signed-in user's profile,' which uses a specific verb and resource. It clearly distinguishes from siblings like update_headline or update_location, leaving no ambiguity about what this 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?

It gives clear context (updating the About section) and a specific safety guideline: read the existing profile first to keep facts intact. It doesn't explicitly state 'when not to use' but the purpose clarity already differentiates it from alternatives, and the read-first advice serves as a practical usage instruction.

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