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

Annotations already declare destructive=true, idempotent=false, openWorld=true. The description adds two genuinely useful behavioral facts beyond them: the LinkedIn session-sync no-op case and the returned advisories. It still never warns that the prior schedule is replaced (the destructive implication) or that the call is non-idempotent.

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?

Three compact sentences with the action front-loaded, followed by the operational caveat and return note. Little waste, though the 'Returns the outcome and informational advisories' sentence is slightly redundant given an output schema exists.

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?

Output schema exists, so return values are covered, and the LinkedIn 20-minute lead time lives in the schema. For a destructive, non-idempotent mutation across an open-world LinkedIn integration, however, the description omits permission requirements and the consequence of replacing an existing schedule.

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 50%, and the description only expands on kind, explaining the auto-detection fallback that the schema does not state. timezone and the lead-time semantics of scheduledFor are documented in the schema itself, so the prose adds only a marginal amount beyond structured fields.

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 (reschedule) and resource (a scheduled note or article), and clarifies that kind may be supplied or auto-detected by id. It does not differentiate itself from the sibling amend_scheduled_item, so an agent still has to guess which mutation to pick.

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?

There is no when-to-use guidance and no mention of alternatives such as amend_scheduled_item or cancel_scheduled_item. The only conditional statement ('pending LinkedIn session sync...') describes behavior, not selection criteria.

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