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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description's 'Delete' is consistent with that. It adds little behavioral context beyond the annotation, though the 'scheduled' qualifier clarifies this operates on scheduled, not published, posts and points to list_scheduled_posts as the source. No contradiction.

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?

Two short sentences with a clear front-loaded action. No filler or repetition that would burden the agent.

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?

For a simple, well-schema'd tool with annotations and an output schema, this is sufficient: required params, source of post_urn, and destructive nature are all evident. An agent can select and invoke it without missing information.

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%, so the schema fully documents all three parameters. The description mostly repeats the schema's provenance for post_urn and adds only a small example format (urn:li:ugcPost:…), which is useful but not substantial. It adds no information about account_id or idempotency_key beyond 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?

Description opens with a specific verb+object ('Delete a scheduled LinkedIn post'), and the object type distinguishes it from sibling tools like update_scheduled_post, delete_conversation, and delete_account. It states exactly what resource is affected.

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 description clearly conveys when to use it (when a scheduled post needs to be removed), but gives no explicit alternatives or exclusion criteria. It provides provenance for post_urn but does not mention update_scheduled_post for modifying rather than deleting. Usage is implied rather than explicitly contrasted.

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