Open LinkedIn edit page

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

The description clearly discloses that the tool opens a browser, requires confirmation, and does not auto-save. This provides important behavioral context beyond what structure provides, especially given no 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?

The description is somewhat repetitive, stating the same opening action twice. It could be more concise, though the risk and confirmation notes are helpful.

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?

The description covers purpose and key behavioral traits but lacks parameter details, usage guidelines, and return information. Given no output schema and no annotations, it is adequate but not thorough.

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 has 33% coverage (only section described), and the description adds no additional meaning to parameters. The 'two-step confirmation' hint relates to confirm but is not explicit. Parameters like approvalToken remain 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 clearly states the tool opens a LinkedIn edit page for manual editing, specifying the action and resource. This distinguishes it from sibling tools like rewrite_about_section or create_linkedin_post, which have different purposes.

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 implies the tool is for manual editing by stating 'no automation, no auto-save,' but does not explicitly state when to use it over alternatives or provide exclusions. No sibling tools are mentioned for comparison.

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