linkedin_profile_custom_url

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing. For a mutation of an account-visible identifier, it omits whether the change is reversible, whether LinkedIn imposes change limits, whether the old URL stops resolving, and what error occurs if the slug is taken.

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?

A single front-loaded sentence that identifies the action and the target field with zero filler. It is efficient, though the brevity comes at the cost of the missing behavioral detail noted elsewhere.

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?

With no annotations, no output schema, and an undocumented parameter, the description is the only source of context and it supplies just one sentence. For a profile-mutating tool it should at minimum cover the session prerequisite and the consequence/irreversibility of changing the public profile URL.

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% and the single parameter 'vanity' carries no schema documentation, but the description's example '(linkedin.com/in/loquesea)' clarifies that the value is the slug portion rather than a full URL, which is genuinely useful disambiguation. It still adds no guidance on allowed characters or the 3-100 length bounds.

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 verb 'Cambia' plus the resource 'URL personalizada del perfil' is specific, and the parenthetical example (linkedin.com/in/loquesea) pins down exactly which profile field is affected. It is distinguishable from sibling tools like linkedin_profile_edit or linkedin_profile_headline, though it never explicitly contrasts itself with them.

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 states only what the tool does, with no when-to-use guidance, no mention of adjacent tools (e.g. linkedin_profile_edit), and no prerequisites such as needing an active session. The agent must infer that this is the tool for the vanity-slug field specifically.

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