drop_linkThe owner's links to drop files you cannot send as text (a scanned PDF) and to manage photos. Needs the owner's sign-in.
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "drop_link"
}
}| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already establish readOnlyHint=true, openWorldHint=false, and destructiveHint=false. The description adds useful auth context with 'Needs the owner's sign-in', but it does not clarify that the tool only returns links rather than performing uploads, nor does it describe link expiry or output shape.
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 compact and front-loads the owner context and auth requirement. The phrase 'and to manage photos' is vague, but overall there is little wasted wording.
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?
With zero parameters and existing annotations, the description covers the auth prerequisite and a general use case. It is still incomplete for a link-returning tool because it does not explain what kind of links are returned, whether multiple links are possible, or how this differs from sibling upload tools.
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?
The tool has zero parameters, so there is no parameter semantics burden. The description does not need to explain inputs, and the baseline for a no-parameter tool applies.
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 hints that this tool returns owner-specific links for dropping files and managing photos, but it never states a clear verb or resource like 'Get upload link'. It does not explicitly distinguish the tool from siblings such as add_photo or upload_report.
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 an implied use case, 'files you cannot send as text (a scanned PDF)', which helps an agent understand when the tool is relevant. However, it provides no explicit when-not guidance and does not name alternatives for photo or report upload scenarios.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.