preview_application_submission

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the tool is disabled by default and requires an approved provider mutation capability, which is real context. But it does not state whether the preview is side-effect-free, what auth is required, or what the preview returns, all important for a mutation-preview tool.

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 short sentences, front-loaded with the action, and the second sentence carries necessary gating information. Minor grammar issue ('a application') does not cause bloat.

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?

The tool has a nested changes payload, two required params, 0% schema description coverage, no annotations, and no output schema. The description covers purpose and capability gating but leaves parameter structure, validation limits, and preview result/next-step behavior unexplained. Incomplete for this complexity.

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 0% with two required parameters: provider (enum linkedin/naukri) and changes (nested array of field/operation/value). The description never mentions these parameters or explains what a 'changes' entry means, so it adds no meaning beyond the schema. For a nested mutation payload, this is a significant gap.

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 'Preview a application mutation,' giving a clear verb and resource. It is understandable in context, but 'application mutation' is broad and it does not distinguish this tool from sibling preview tools or explain what application fields may be changed. Clear but not maximally specific.

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?

It gives a capability precondition: disabled by default and available only when the provider advertises an approved mutation capability. However, it does not explicitly say to use this before execute_confirmed_mutation, nor does it point to discover_provider_capabilities for checking the gate. Usage is implied rather than fully spelled out.

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