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

Annotations declare readOnlyHint=false and openWorldHint=true, which is surprising for something called a 'dry run', yet the description never clarifies whether anything is actually sent or mutated. It does add useful domain context about what a drop is, but leaves the central behavioral question (side effects, idempotency) unaddressed.

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 alias relationship is front-loaded in the first clause, which is the most important info. The second sentence defining 'drop' is long and somewhat tangential to the dry-run operation, but still earns its place as domain context.

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-read-only, open-world tool with no output schema, the description omits the essential details: what a dry run produces and whether it has side effects. The drop definition does not compensate for the missing operational description.

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% and both parameters are fully documented with sources and formats, so the schema carries the burden. The description adds no parameter meaning beyond 'same arguments', which is the expected baseline.

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 states that this is the alias of lnkdrp_dry_run_drop with identical arguments and answers, which helps distinguish it from the many siblings. However it never says what a dry run actually does – it only defines the domain term 'drop'. The operation's purpose is left to be inferred from the name.

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?

By declaring 'same as lnkdrp_dry_run_drop, same arguments and same answers', it implies the two are interchangeable and routes the agent to the canonical tool. It gives no explicit when-to-use/when-not or preference ordering between the alias and the canonical name.

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