social_media_posting_attach_linkedin_page_profile

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

Annotations already indicate readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true. The description adds no behavioral context beyond the word 'attach', such as side effects, reversibility, or whether existing attachments are replaced. No new information is provided beyond what the annotations already state.

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 extremely short (one phrase), but this is under-specification rather than effective conciseness. It lacks structure and fails to front-load useful detail. While not verbose, it does not earn its place because it adds minimal value beyond the tool name.

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 complexity (8 parameters, no output schema, and a clear need to differentiate from sibling attach tools), a one-line description is wholly inadequate. It provides no context on workflow, parameter relationships, or expected behavior, leaving the agent with insufficient information to use the tool 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 description coverage is only 38%, and the description does not explain any parameter. Many fields (urn, name, type, avatar, originId) lack descriptions in both the schema and the tool description. The description adds no semantic meaning to any parameter, failing to compensate for the low schema coverage.

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 'Attach linkedin pages and profile' clearly states a specific verb (attach) and resource (LinkedIn pages and profile), and the tool name itself distinguishes it from sibling tools for other platforms. It is not a tautology and conveys the basic action, though it leaves the broader context (e.g., attaching to what) implied.

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?

No usage guidance is provided. The description does not indicate when to use this tool over the sibling 'attach' tools (e.g., attach_facebook_page_group, attach_instagram_page_group), nor does it mention prerequisites or a typical workflow. The agent is left to infer intent from the name alone.

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