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

Annotations already flag destructiveHint=true, readOnlyHint=false, openWorldHint=true, and idempotentHint=false. The description adds 'Refresh,' which signals a side effect beyond pure reading, but it does not explain what refresh destroys, what permissions are required, or why the operation is destructive.

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?

Two concise sentences with the purpose front-loaded. The second sentence restates return fields that are already available in the output schema, adding minor redundancy, but overall it is efficient.

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 definition is largely complete for a simple list/refresh tool: it states the resource, scope, return fields, and annotations cover safety. The main gap is the unexplained destructive refresh behavior and lack of explicit usage guidance, but the output schema and annotations reduce the burden.

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%, so the two optional parameters (writer, workspace) are fully documented in the schema. The description adds no parameter-specific meaning, which is acceptable given the high 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?

States a specific verb and resource: lists LinkedIn personal profiles and Company Pages available for Notes. The 'for Notes' scope differentiates it from list_linkedin_article_destinations, though it does not explicitly name that sibling as out of scope.

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?

Usage is implied by 'available for Notes,' suggesting it should be used when selecting LinkedIn destinations for note publishing. However, there are no explicit when-to-use, when-not-to-use, or alternative-tool instructions.

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