td_save

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

With no annotations, the description must carry the full burden of transparency. It mentions the optional new path, but does not disclose potential overwriting behavior, behavior when no project is loaded, or side effects. This is a significant gap for a save operation that could modify or replace existing files.

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 a single, focused sentence. It front-loads the core action and includes the key optionality. Every word adds value, with no fluff or repetition.

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 tool's simplicity (one optional parameter) and the presence of an output schema, the description covers the primary functionality well. It could mention overwriting implications, but overall it is reasonably complete for a save operation.

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 schema coverage is 0%, so the description must compensate. The phrase 'optionally to a new path' adds meaning to the 'file' parameter, indicating it is a destination path and that omitting it likely saves to the original location. However, it stops short of specifying path format or behavior when the parameter is null.

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 the action ('Save the .toe project') and the optional path parameter, using a specific verb and resource. It does not explicitly differentiate from sibling tools, but the action is unambiguous enough for a save operation.

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 implies usage (when you want to save a project), but offers no explicit guidance on when to use it over alternatives like td_create or td_build, nor any prerequisites or conditions. It is neither misleading nor detailed enough to earn a 4.

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