appcrane_cat

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

Beyond the lack of annotations, the description explicitly discloses read-only nature, root restrictions, file size refusal, and a truncation workaround, providing comprehensive behavioral transparency.

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 extremely concise, with two sentences that efficiently convey purpose and key constraints, front-loading the main action.

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?

Despite no output schema, the description covers constraints and behavior adequately for a file-reading tool. It could mention return format, but it's implied as file content.

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 description adds no new information about parameters beyond what the input schema already provides (e.g., path must start with /app or /data), but schema coverage is 67%, so 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 clearly states the verb 'Print' and the resource 'contents of a file inside a running app container', distinguishing it from sibling tools like appcrane_cp (copy) and appcrane_ls (list).

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 provides usage context: read-only, restricted to safe roots, and file size limit, with a suggested workaround for large files. It does not explicitly mention when not to use or alternatives like appcrane_cp.

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