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

Annotations cover the safety profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false), so the bar is lower. The description still adds value beyond structured data by disclosing the required auth scope (compliance:write) and the semantic effect on compliance status, though it says nothing about duplicate-link behavior or error conditions.

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?

Front-loaded purpose followed by scope, required params, and a resolution tip in three tight sentences. The re-listing of required parameter names is mildly redundant with the schema, keeping it short of a full 5.

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 non-idempotent mutation/link tool with annotations covering the safety hints and no output schema, the description covers auth scope, intended effect, and id resolution. It is nearly complete, though it could note what happens if the link already exists.

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 all four parameters including weight (default 1) are already documented in the schema. The description merely re-lists the three required ids and gives a resolution hint, adding no syntax or semantic detail beyond what the schema provides. Baseline 3 is correct.

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 and resource with scope: 'Link a PM schedule to a compliance item, so completing the schedule keeps the item compliant.' This distinguishes it from sibling create_compliance_item and create_pm_schedule, making the junction/link semantics immediately clear.

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?

Provides a prerequisite (compliance:write scope) and concrete setup guidance: 'Resolve both ids first with list_compliance_items and list_pm_schedules.' This tells the agent what to do before invoking, though it does not explicitly contrast this link-creation with the sibling create_* tools.

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