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

With no annotations, the description carries the full burden, and it does disclose useful traits: the save is free (0 credits), targets the caller's workspace, and notes are private. However, it is silent on behavior that matters for a write tool — overwrite vs. duplicate-label handling, whether folders are created implicitly, and permission requirements.

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 core action front-loaded and no filler; the cost note is genuinely useful for an agent budgeting calls. Slightly more compression or structure (e.g., grouping the saved payload fields) would earn a 5.

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 4-required-parameter write tool with a nested object, zero schema descriptions, no annotations, and no output schema, the description is too thin. It does not say what is returned (an ID, a workspace item) or how the saved query relates to later retrieval via get_research_workspace.

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 there are 4 required parameters including a nested query object. The description names the query, folder, and notes concepts but never explains 'label', nor any of the nested query fields (tool enum with 8 values, mode enum with 5 values, q, region, limit) — a significant gap the schema does not fill either.

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 and resource: 'Save a standalone site-tool query' scoped to 'the caller workspace, with a folder and private notes'. The word 'standalone' faintly separates it from bulk/monitoring siblings, but no sibling is named, so differentiation still requires opening the tool list.

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 or when-not-to-use guidance and no reference to alternatives such as manage_research, monitor_research, or get_research_workspace. 'Standalone' is the only hint that this is not the bulk/monitored path, which is too thin to route an agent reliably.

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