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

Adds real context beyond annotations: posts count against a daily quota, and the agent should show the user the full text before calling. Annotations only supply the safety profile (readOnly=false, destructive=false, openWorld=true). The idempotency behavior is left to the schema rather than restated here.

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 action and dense with useful detail. Slightly redundant: the schedule/omit behavior is stated twice ('Set scheduled_at … omit it to publish immediately' then 'Publishes now or schedules'), and the stray 'scheduled_time' term adds noise.

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 an output schema present and annotations covering the safety profile, the description is nearly complete: it covers modes, media routing, quota, and a user-confirmation guardrail. The inconsistent 'scheduled_time' reference is the only notable gap for an agent parsing the scheduling parameter.

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% (baseline 3), but the description adds genuine value by mapping media_urn to the correct URN format per case and restating the scheduled_at scheduling semantics. Minor confusion: it later refers to 'scheduled_time', a name not present in the schema.

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 ('Create or schedule a LinkedIn post') and immediately delineates the two modes. Distinguishes itself from siblings like create_multi_photo (referenced for the multi-image URN) and update_scheduled_post.

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 conditions: single image → digitalmediaAsset URN, multiple images → fsd_multiPhoto URN from create_multi_photo, set scheduled_at to schedule, omit to publish now. Routes the agent to the correct sibling and states the alternative publishing modes.

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