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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the write/submit nature is conveyed structurally. The description adds the destination ("LinkMCP team") and a user-consent guardrail, but it does not explain the odd destructiveHint for what is a submission tool, whether submission is reversible, or what confirmation the caller receives. With annotations covering the safety profile, this modest added context merits a 3.

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 tight sentences with zero redundancy, purpose first and the usage restriction second. Every clause earns its place.

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 three-parameter submission tool with no output schema and full schema coverage, the description supplies purpose and the when-to-use guardrail that the structured fields cannot. It stops short of describing post-submission behavior (confirmation or acknowledgement), a minor gap rather than a blocking one.

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%, so type/message/context are fully documented in the schema, including per-enum meanings and nested context fields. The description only echoes the enum values already listed in the schema, adding no syntax, format, or sizing guidance beyond it. Baseline 3 applies when the schema does the heavy lifting.

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+destination: "Send the user's feedback, feature request, bug report or help request to the LinkMCP team." This is unmistakably distinct from every sibling, which are all LinkedIn data/action tools. An agent can identify the operation without opening the schema.

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?

"Use it only when the user asks to send feedback or to contact LinkMCP support" gives an explicit trigger and an implicit exclusion (do not use proactively). It does not name alternatives, but no sibling is a plausible substitute for this tool, so the omission is harmless.

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