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

With no annotations, the description carries the full burden but does disclose two real behavioral facts: the save is free (0 credits) and the notes are private. It is silent on overwrite/duplicate behavior, auth requirements, and what a failed save does, which matters for a 4-required-param write 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 scope, ending with the non-obvious cost fact. No filler or repetition of the field names.

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?

A mutation tool with no annotations, no output schema, and four parameters at 0% schema coverage needs more than one sentence of behavior. The agent still cannot tell what goes in the nested query object or how a saved item behaves afterward.

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 only implicitly touches 'folder' and 'notes' (privacy) plus 'query' as a site-tool query. The required 'label' is never mentioned, and the nested 'query' object's expected shape is left entirely unexplained in both schema and description.

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?

Specific verb+resource+scope: 'Save a standalone site-tool query in the caller workspace'. It also names the payload (folder, private notes), so an agent knows exactly what is stored. It does not explicitly contrast itself with manage_research or monitor_research, but the word 'standalone' gestures at the distinction.

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 explicit when-to-use/when-not statement or named alternative. The qualifier 'standalone' implicitly separates this from the managed-research siblings (manage_research, monitor_research), which is a usable but indirect signal.

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