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

Annotations already declare readOnly, idempotent, non-destructive, openWorld, so safety is covered; the description adds genuinely useful behavior beyond that: the ~200 KB text limit, ~1 MB image limit, and the type+size fallback for other files. It does not mention auth requirements or error behavior for missing/oversized files, keeping it below a 5.

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?

A single tightly-packed sentence plus the endpoint, with the core action front-loaded and the size/return semantics following. No filler.

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 return-value burden and does so well by explaining text/image/type-size outcomes. It stops short of describing failure modes (missing file, exceeding limits) but is otherwise complete for a simple read tool.

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 both parameters (path and optional email) are already fully documented in the schema. The description adds no syntax or format detail beyond 'by path', so the baseline 3 applies.

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 (read) and resource (a file from the Muse workspace) scoped by path, and describes the return behavior for each file category. It is clearly distinguishable from siblings like muse_list_files, muse_search_files, and muse_write_file.

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?

Usage is implied by 'by path' — an agent infers this is the tool to fetch a single known file — but there is no explicit when-to-use guidance and no mention of alternatives such as muse_search_files for discovering a path. Adequate but with a clear gap.

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