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

With readOnlyHint already covering safety, the description layers on rich behavior: never names strangers, exposes no impression/follower metrics, links drafts via /graph/object/<draft_id>, ends with /linkedin/manager when a plan exists, and specifies special handling for null plan and in_brand_brief (hide plan concept, never link the manager page).

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 core purpose is front-loaded, but the paragraph then sprawls into rendering directives (exact markdown link templates, /your-day?show=brand URLs) that are implementation detail rather than selection guidance. Every sentence is arguably useful for correct output, yet the density and run-on structure hurt scanability.

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, so the description must carry the return-value burden, and it does: it enumerates the sections (plan/drafts, posts, engagers, switch state, nudge status). It also covers the null-plan and in_brand_brief edge cases completely.

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 no parameters, so the baseline is 4; there are no inputs whose semantics could be unclear or need compensating description.

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+resource ('How this week is going on LinkedIn against the user's own post plan') and enumerates the exact contents returned: plan subjects with draft status, this week's posts mapped to plan subjects, and known engagers. It also demarcates itself from analytics siblings by declaring it has no impressions/follower counts and never names strangers.

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 concrete trigger phrasings ('how's my LinkedIn week going', 'did I post what I planned', 'who engaged with my post') and explicit when-not guidance ('do not offer' impressions/followers). It stops short of naming a specific sibling tool to use instead, so it is clear rather than fully routing.

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