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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is partially covered. However, the description adds nothing beyond that: it does not warn that repeated calls create duplicate reshares (non-idempotent), nor does it mention the visibility restriction that CONNECTIONS applies only to personal accounts (that detail lives only in the schema).

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 with no filler or repetition. It is efficient, but its brevity is partly under-specification rather than tight editing.

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 four well-described parameters and annotation coverage, the definition is minimally viable. For a non-idempotent write tool with no output schema, it should still say what the call returns (e.g. the new reshare URN) or note duplicate-creation behavior; that gap keeps it at adequate rather than complete.

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 100%, including detailed URN-format warnings for 'parent' and the personal-account constraint on visibility, so the schema carries the parameter burden. The description's mention of 'optionally with commentary' merely restates the schema and adds no syntax or format detail of its own.

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?

States a specific verb (reshare/repost) and resource (an existing LinkedIn post) plus the destination (your feed) and the optional commentary. It is distinguishable from create_post, though it never names or contrasts a sibling explicitly.

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 offers no when-to-use or when-not-to-use guidance and no alternatives: e.g. create_post vs reshare, or when to prefer resharing over quoting with commentary. The requirement that the target be an existing post is implied only by the word 'existing'.

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