ultrathink_save

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

No annotations are provided, so the description carries the full burden and only conveys that this is a write. It says nothing about what is returned (an ID?), whether duplicate titles overwrite or create a second entry, permission or org-sharing behavior behind visibility, or what happens if type=link without a url.

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 with the action leading and the usage examples second – appropriately sized and front-loaded. The second sentence borders on generic ('other knowledge') but does not waste much space.

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 rich input schema compensates for much of the missing detail, and no output schema exists so return values needn't be spelled out. However, for a 6-parameter mutation tool with zero annotations, the description leaves an agent without the create-vs-update semantics or failure behavior it would need to call this confidently.

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%, so both enum values and each field's meaning (url required for link, visibility private/org, type default note) are already documented. The description adds nothing beyond restating a subset of the content types, so the baseline 3 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?

States a specific verb+resource ('Save an entry to Ultrathink knowledge base') and illustrates the kinds of content it accepts. It separates itself from the only sibling, ultrathink_search, by implication (save vs. search), though it never names the alternative.

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?

The second sentence gives examples of when to reach for it (notes, ideas, links, snippets), which implies the trigger condition. There is no explicit when-not guidance, no mention of updating vs. creating, and no reference to ultrathink_search as the retrieval counterpart.

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