Change the broadcast alias or download directory for the LocalSend MCP server to control how the AI agent appears on the network and where incoming files are saved.
Update LocalSend MCP server configuration (alias, download directory, or transport).
| Name | Required | Description | Default |
|---|---|---|---|
| alias | No | New broadcast alias for the AI agent (e.g. 'Antigravity Agent'). | |
| downloadDir | No | Directory path where incoming files are automatically saved. |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure, but it only states that configuration is updated. It does not say whether changes persist, require a restart, take effect immediately, or are reversible; the mention of 'transport' also hints at a capability not present in the schema.
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 one compact sentence with the operation and target front-loaded. It wastes no words, though the unsupported 'transport' item is an accuracy issue rather than a structure issue.
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 two-optional-parameter tool, the schema plus short description is mostly sufficient to form a call. However, with no annotations and no output schema, the description omits whether at least one parameter must be supplied, whether the update is incremental, and what kind of confirmation or error the agent should expect.
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 the schema already fully documents alias and downloadDir. The description adds no useful meaning beyond that and instead introduces 'transport' as a third setting that is not represented in the schema, which is misleading for parameter selection.
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 uses a specific verb ('Update') and names the resource ('LocalSend MCP server configuration'), making the tool's purpose immediately recognizable against siblings like localsend_send and localsend_status. Clarity is slightly reduced because it lists 'transport' as an updatable setting even though the input schema only exposes alias and downloadDir.
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?
There is no guidance about when to call this tool versus alternatives, no prerequisites, and no exclusions. The only usage signal is the implied role of a configuration-update tool, which the agent must infer from the name and sibling contrast.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.