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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the path-format context (Fine Structure app file API, external docs), which is useful. However, it does not disclose truncation behavior implied by the max_chars default, non-existent-file handling, or return shape. With annotations carrying the safety burden, a 3 is appropriate.

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 sentences with no filler; the primary purpose is front-loaded and the path-API pointer is a single adjunct clause afterward. The only minor inefficiency is that the external-docs link could arguably be shortened, but the sentence count and ordering are economical.

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?

Adequate for a simple single-file read tool whose annotations cover the safety profile. It lacks an output schema and does not describe error behavior, truncation, or response format; it defers path semantics to an external doc. Acceptable but not richly complete for an agent that must call it correctly.

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 coverage is 100%: path, app_id, and max_chars are all self-describing in the schema. The description adds nothing beyond 'one source file' that isn't already in the property definitions, so it sits at the baseline 3.

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-resource pair ('Read one source file from an app's virtual filesystem') and deliberately emphasizes 'one', which differentiates it from the sibling read_app_files. The path-API reference further pins down exactly what kind of file is targeted.

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 'one source file' phrasing implies a contrast with the plural sibling read_app_files, but the description never explicitly says when to prefer this tool over read_app_files, write_app_file, or patch_app_file. Usage context is implied rather than stated, so an agent must infer the boundary.

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