linkedin_profile_about

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

With no annotations, the description carries the full behavioral burden, yet it only says the About section is rewritten. It does not disclose that a write only happens conditionally via a separate 'save' flag, whether publishing is live/irreversible, what happens to existing About content, or any auth/rate-limit requirements.

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?

It is a single front-loaded sentence with zero filler, which is structurally clean. However, the extreme brevity comes at the cost of substance rather than from efficient packing of information.

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 profile-mutating tool with no annotations, no output schema, and 0% parameter coverage, the description leaves critical gaps: the effect on live profile data, the role of the 'save' flag, and the content length limit. It is not adequate for an agent to call this tool safely.

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 description coverage is 0%, so the schema documents neither parameter. The description likewise says nothing about 'text' (the new content, max 2600 chars) or 'save' (whether changes are persisted), leaving the most consequential parameter, the save toggle, completely unexplained.

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 names a specific verb ('Reescribe') and a specific resource (the 'Acerca de'/About section), which lets an agent distinguish it from headline, image, or custom-URL siblings. It is clear but does not differentiate itself from a general sibling like linkedin_profile_edit, and it doesn't clarify whether 'rewrite' means generate-and-replace or merely update stored text.

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?

There is no statement of when to use this tool versus linkedin_profile_edit or linkedin_profile_read, and no prerequisites (login/session state) are mentioned. The single sentence implies an editing action but gives the agent nothing to route on.

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