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

Annotations already declare readOnly, idempotent, non-destructive and non-open-world, so the safety profile is covered. The description adds real behavioral context beyond that: entries contain tool sequences, prerequisites and full instructions, and playbook_id narrows the response to one playbook. It does not discuss pagination or catalogue size, but for a static read-only catalogue that is minor.

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 'START HERE' and tightly organized, but the when-to-use guidance is stated twice ('Call this first when the user asks what you can do... or when a request is vague' then 'Use first for a vague request or what can you do'). One of those sentences could be dropped without loss.

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?

An output schema exists, so return structure need not be explained, and the description covers everything else an agent needs: that this is a discovery entry point, what each entry contains, how to drill into one, and when to skip it entirely.

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 baseline is 3. The description goes slightly beyond the schema by explaining the intent of playbook_id (retrieve one playbook's instructions 'and then follow them') and flagging that include_instructions produces longer output, which helps an agent decide whether to set it.

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 ('Return the catalogue of ready-made LinkedIn playbooks') and immediately reframes it as 'what this server can actually accomplish, as named workflows rather than raw endpoints'. That framing distinguishes it from every sibling, which are all single-action endpoint tools.

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?

Gives explicit when-to-use ('Call this first when the user asks what you can do... or when a request is vague') and explicit when-not ('not needed when the user names a precise action'). It also names the follow-up behavior (pass playbook_id, then follow the instructions), leaving nothing to inference.

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