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

Annotations only declare idempotent/non-destructive flags, but the description goes far beyond: stars are personal to the API-key owner and invisible to recipients, repeats report unchanged, the 200-star ceiling triggers validation with details.code stars_limit_reached, and result text is untrusted author content. This is exactly the behavioral context an agent needs.

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?

Front-loaded with the core verb and scoping, then ordered into behavior, return shape, edge cases, and safety. It is dense at roughly nine sentences, but each carries distinct information; slightly tighter grouping would be ideal.

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?

There is no output schema, and the description compensates fully by enumerating the return collections (changed, unchanged, notFound with its causes, then the full starred list) as well as the limit failure mode. Nothing an agent needs to call it correctly is missing.

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 coverage is 100% and already documents both parameters (docIds 1-50, starred default true). The description reinforces the meaning of starred:false and the 50-document cap but adds no syntax or format detail beyond the schema, so baseline 3 applies.

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?

Specific verb+resource: 'Star (or ... unstar) up to 50 documents'. It clearly distinguishes itself from read-side siblings like lnkdrp_list_starred and from unrelated mutation tools such as lnkdrp_tag by naming the exact action and its effect on the key owner's sidebar.

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?

It states both directions of use (star by default, unstar with starred:false), notes repetition safety, and explains the containment edge case. It never explicitly names alternative tools or a when-not-to-use condition, so it stops short of full routing guidance.

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