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

Annotations already establish readOnlyHint, idempotentHint and destructiveHint=false, but the description goes well beyond them: sidebar ordering, exclusion of deleted/archived and private-room documents, star persistence on restore, the project-contained-document edge case, and an explicit prompt-injection warning about untrusted author/reader text. That is substantial behavioral context an agent cannot get from the 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 primary scope (owner's starred docs, sidebar order) is front-loaded in the first clause, and each subsequent sentence covers a distinct edge case or safety note. It is dense and slightly run-on, but no sentence is filler.

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 parameters and no output schema, the description's only real obligations are scope, filtering behavior and result trustworthiness, all of which it covers. The mention of titles, summaries and viewer-supplied text also implicitly signals the shape of returned content, which is sufficient here.

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 tool takes zero parameters, so per the rubric the baseline is 4. There is nothing for the description to disambiguate, and it correctly avoids inventing parameter semantics.

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 names a specific verb and resource ('The key owner's starred documents in this workspace, in their sidebar order') and scopes it to the key owner rather than all workspace documents. It implicitly separates itself from siblings such as lnkdrp_list_docs, lnkdrp_list_deleted and lnkdrp_star_docs by stating that deleted/archived documents are excluded and that stars persist.

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 inclusion/exclusion rules make the tool's applicability inferable, but there is no explicit when-to-use guidance and no sibling is named as an alternative (e.g. 'use lnkdrp_list_docs for the full workspace listing'). The agent must infer routing from the sibling names rather than being told.

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