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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, so the safety profile is covered. The description adds value beyond annotations by stating the call is free and that the returned data contains the id that delete_linkedin_lead_subscription consumes. It does not mention pagination or auth details, but these are less critical given the annotations.

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 description is compact: one sentence plus the 'Read-only, free' tag, with no filler. The clause 'with the id delete_linkedin_lead_subscription takes' is grammatically awkward, but the resource is front-loaded and the whole definition is appropriately sized for a simple list operation.

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 list tool with no required parameters and no output schema, the description tells the agent what is listed, the Page/ad-account scope options, that it is read-only and free, and that results contain the id needed for deletion. It omits leadType semantics and pagination, but openWorldHint and the absence of required parameters reduce the risk of incorrect invocation.

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 schema documents pageId and adAccountId, and the description reinforces the Page-versus-ad-account axis with 'registered on a LinkedIn Page or ad account.' However, it adds no guidance for the undocumented leadType parameter, leaving 33% of parameters without semantic coverage. The description is helpful but largely redundant with the schema's existing parameter notes.

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?

The description precisely identifies the resource as lead notification webhooks registered on a LinkedIn Page or ad account, clearly distinguishing it from sibling tools like list_linkedin_lead_forms, list_linkedin_leads, and list_linkedin_lead_events. It also notes the returned id feeds delete_linkedin_lead_subscription, reinforcing what the tool returns. The grammar is slightly awkward, but the purpose is unmistakable.

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 makes clear this is for inspecting existing webhook registrations on either a Page or ad account, and the reference to delete_linkedin_lead_subscription signals it as the lookup step before deletion. It does not explicitly contrast with subscribe_linkedin_leads or list_linkedin_lead_events, but the registered-webhooks framing provides clear context without exclusions.

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