save_summary

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

The description adds behavioral context beyond annotations by noting that the tool synchronously updates full-text and vector indexes. Annotations indicate readOnlyHint=false (write operation) and destructiveHint=false (non-destructive), which are consistent. The description does not detail error handling or uniqueness constraints, but the synchronous index update is a useful disclosure.

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 front-loaded with the core purpose in one line, followed by a structured parameter list. It is concise but could be shortened by not repeating schema content. The format is clear and easy to parse.

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 presence of an output schema (Dict with success and message), the description need not detail return values. It covers all input parameters and the indexing side effects. However, it lacks guidance on uniqueness enforcement and error scenarios. The tool is moderately complex, and the description is largely complete.

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 description lists all parameters with brief descriptions, but the input schema already provides identical descriptions for each property. Since schema description coverage is effectively high (each property is documented), the description adds no new semantic value. Per guidelines, baseline 3 is appropriate when schema covers parameters.

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 clearly states 'save session summary to database, synchronously update full-text and vector indexes,' providing a specific verb and resource. The name 'save_summary' further reinforces the action. It distinguishes itself from siblings like 'update_summary' and 'get_summary_by_id' by focusing on creation and indexing.

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 description does not explicitly state when to use this tool versus alternatives like 'update_summary' or 'search_summaries.' The purpose implies it is for creating a new summary, but no usage context or exclusions are provided. This leaves room for an agent to misuse the tool.

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