ContextSave

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

Annotation contradiction: description claims to save (write) but readOnlyHint=true indicates read-only. No other behavioral traits disclosed (e.g., file overwrite behavior, output). Flagged as annotation contradiction.

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?

Description is concise with two clear sentences, though the bullet-point style is less formal. Front-loaded with main action, but includes minor implementation details (e.g., random 3 word id).

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?

No output schema and no description of return value or behavior. Does not explain what the tool outputs or side effects. Missing key context for a complete understanding.

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 has 0% coverage, but description provides guidance for 'id' (random unique id) and 'project_root_path' (empty for none). However, 'description' and 'relevant_file_globs' lack explanation. Adds marginal value beyond schema.

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?

Description states it saves description and file contents to a text file, which implies a write operation. However, the readOnlyHint annotation contradicts this, making the actual purpose unclear to the agent.

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?

No guidance on when to use this tool vs siblings like FileWriteOrEdit or Initialize. Only includes brief instructions for parameters but no usage context or alternatives.

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