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

No annotations are provided, so the description carries full responsibility. It fully discloses the write behavior, content format (base64), creation of parent directories, and destructive overwriting. This is significant behavioral context for a mutation tool. It doesn't mention return values or error conditions, but these are not critical for a simple file push.

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 sentences, each directly useful: the core operation, the primary use case, and the overwrite behavior. No filler. The most critical details are front-loaded.

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?

For a tool with 4 parameters and no annotations or output schema, the description covers the essential semantics: what it writes, where it writes, how it handles directories, and its destructive nature. It points to the sibling ios_file_list for bundleId semantics, which helps grounding. Minor gaps like return format or permissions do not hinder correct invocation.

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 100%, so the schema fully documents all four parameters. The description adds marginal value by explaining the purpose of bundleId (root selection seed app container) and how content is interpreted, but it does not replace or significantly extend the schema descriptions. Baseline 3 is appropriate.

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 states a specific action ('Write a file onto an iOS device from base64 content'), names the resource, and adds key behavioral details (creating parent directories, overwriting). It clearly distinguishes itself from sibling file operations like ios_file_pull (reading), ios_file_delete, and ios_file_copy/move.

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 gives a concrete use case: seeding an app's own container with fixture data, config files, or test databases before launching it. It mentions the bundleId root selection consistent with ios_file_listcars, which helps an agent understand when to use this over other file tools. However, it does not explicitly state when NOT to use it (e.g., shared media directory) or list alternate tools.

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