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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description adds the meaningful context that discovered posts and already-queued comments are preserved and that resumption is possible via setup_linkedin_monitoring. That preservation guarantee is exactly what an agent needs before taking an irreversible-sounding action, though permissions/on_behalf_of behavior and error conditions are left to the schema.

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 effect and the preservation/resume caveats are front-loaded in a tight summary, and the returns block is compact. The XML-style tag scaffolding is slightly heavier than plain prose would be, but no sentence is wasted.

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 no output schema, the description usefully supplies the return shape (status/name/message) and covers state effects and the resume path. Only minor gaps remain, such as what happens if the name doesn't match an existing monitor.

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% (all three parameters, including on_behalf_of's agency-client semantics, are documented in the schema), so the description is not required to carry parameter meaning. It adds nothing beyond the schema's own wording, which is the baseline case for full coverage.

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?

Specific verb+resource: 'Stop a LinkedIn post monitor — no more scheduled runs.' It immediately distinguishes itself from the sibling setup_linkedin_monitoring by describing the inverse operation, and the effect (scheduled runs stop) rules out read-only siblings like get_linkedin_monitors.

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 tells the agent how to reverse the action ('Re-run setup_linkedin_monitoring with the same name to resume'), which implies the inverse use case, but it never states explicitly when to choose this tool over alternatives such as edit_monitor_members or leaving the monitor in place. Usage is inferable rather than stated.

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