save_project

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

Annotations already declare the safety profile (not read-only, non-destructive, idempotent, closed-world). The description adds genuine context beyond that: the version is immutable, persists only locally, never sent remotely, and is shared with an independent editor via the local store. It omits overwrite/return behavior, but with annotations present this is strong added value.

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?

Three short, front-loaded sentences with no filler; the core action leads. Slightly terse given the unexplained parameters, but no sentence is wasted.

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 it is a mutation tool with annotations covering safety and no output schema, the description conveys storage semantics and sharing well. It falls short by leaving the required 'schema' argument unspecified and introducing a 'project' classifier that has no matching parameter.

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%, so the description must compensate for both parameters. It loosely references topic via 'classified by topic', but never explains the required 'schema' parameter, and its mention of classification 'by project' maps to no actual parameter, which risks confusing the agent about what to pass.

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: saving an immutable local native schema version. It is distinguishable as a persistence/storage operation. However, it does not name or differentiate itself against siblings like create_schema_from_template, validate_schema, or export_sql, so an agent must still infer the boundary.

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 says the save is local with no remote sending, which lightly implies a use context, but gives no explicit when-to-use guidance and no alternatives. It never tells the agent when to prefer this over validate_schema or create_schema_from_template.

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