session_write_file

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

No annotations are provided, so the description must disclose behavioral details. It mentions 'relative path, no escapes' and implies a write operation, but it doesn't state whether the file is overwritten, if directories are created, or any error conditions. It adds some context (seeding input) but lacks depth on side effects.

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 concise sentences with no fluff. The purpose is front-loaded, and every word adds value. Efficient and clear.

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?

The tool is simple but with no annotations and no output schema, the description should cover important behavioral aspects. It explains the use case and path constraint, but omits details like overwrite behavior, error handling, and return values. For a basic write, it's adequate but incomplete.

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 has no descriptions (0% coverage), so the description must compensate. It clarifies that 'path' is relative and cannot escape the workspace, and 'content' is the data to write. However, it doesn't explain 'session_id' beyond its name, and no format or constraints for content are given. Some meaning added, but not comprehensive.

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 tool writes a file into a session workspace, specifying the verb 'Write' and resource, with an additional constraint 'relative path, no escapes'. It also distinguishes from sibling tools like session_read_file by focusing on writing and seeding input data.

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?

It provides a clear use case: 'Use this to seed input data for executed code.' This implies when to use it, though it doesn't explicitly mention alternatives or when not to use it. The constraint on relative paths is also helpful. Slightly more explicit exclusions would make it a 5.

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