save_weblink

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only says 'save a weblink to a space', implying a mutation but providing no details about required permissions, side effects, errors, response behavior, or what happens to existing data. This is insufficient for a write operation.

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 a single concise sentence with no wasteful words, and it is front-loaded with the verb. However, it is so brief that it lacks structure or elaboration, making it more under-specified than appropriately structured.

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?

Given the nested requestBody with six properties, no annotations, and no output schema, the description is far too minimal. It provides no information about required fields (e.g., spaceId, url), optional enhancements (tags, mdText), or what the response looks like, leaving the agent without enough context to invoke the tool correctly.

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%, and the description does not name any parameters. It vaguely maps 'weblink' to the url field and 'space' to spaceId, but completely ignores tags, mdText, titleOverwrite, descriptionOverwrite, and the nested requestBody structure. An agent would have to guess at the meaning of these fields from the schema alone.

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 ('save'), resource ('weblink'), and destination ('space'), which makes the core purpose clear. It is distinguishable from sibling tools like 'get_spaces' and 'save_to_daily_note' due to the explicit target, but it does not explicitly name alternatives or edge cases.

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 on when to use this tool vs. alternatives like 'save_to_daily_note', no prerequisites, no context about typical scenarios, and no mention of limitations. The description simply states what it does, not when to choose it.

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