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

Beyond the readOnlyHint annotation, the description discloses important behaviors: large files are truncated with a truncated flag and real byte size, binary files are reported as binary rather than mangled, and server.js content is included even though it is not served to visitors. It also warns that returned data may be untrusted and must not be treated as instructions, adding safety context annotations cannot provide.

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 longer than typical, but every sentence earns its place by covering purpose, behavioral edge cases, tier-specific guidance, an alternative tool, and a security warning. It front-loads the core purpose before moving into usage details, though the warning could arguably be shorter without losing impact.

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?

With no output schema, the description carries the burden of explaining return values, and it does so sufficiently: file lists with size and server-code status, file contents, truncation behavior, and binary handling. It also covers prerequisites (tier 4), the relationship to dropyour_replace, and safety caveats, making it effectively complete for an agent to invoke 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?

The schema only documents path, leaving dropId with just a pattern; the description compensates by explaining path behavior in depth: omitting it returns the file list, while providing it returns file content plus metadata about truncation and binary handling. It does not explicitly describe dropId's meaning, but the tool name and sibling context make it reasonably inferable.

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 a specific verb and resource: reading the files of a GRADUATED app's currently served version, not the pre-graduation seed. It distinguishes itself from sibling tools like dropyour_read_content by explicitly contrasting tier 4 vs tiers 1-3 behavior, so an agent can pick the correct tool.

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 explicit when-to-use guidance: use it before dropyour_replace because a graduated app is replaced whole. It also states when not to use it (tiers 1-3) and names the alternative (dropyour_read_content), plus differentiates list vs content usage based on whether path is supplied.

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