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

Annotations already declare readOnlyHint=true and destructiveHint=false, so 'Read-only: it writes nothing' largely restates them. The added value is the disclosure that it computes an ordering/placement as a preparation step for organize_save, but the opaque phrasing ('last standing whole', 'the parking lot') leaves the actual behavior unclear.

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?

One dense sentence plus a fragment; it is short, but jargon like 'since the last standing whole' and 'the parking lot' spends words without conveying meaning to an uninitiated agent. The read-only and ordering facts are correctly 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?

With one simple required param, no output schema, and annotations covering the safety profile, the description supplies the key remaining facts: no writes occur and it precedes organize_save. Only the return's shape ('names the earlier notes and the parking lot') is left vague, which is a modest gap.

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% and the single home_path parameter is documented in detail with storage-prefix syntax. The description adds nothing about the parameter, so 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?

The verb+resource is buried in project-specific jargon: 'Reads the record's full inventory and complete contents, places the staged notes since the last standing whole after them.' An agent can infer it is a read/preparation step, and the closing line 'Runs before organize_save' names a sibling, but a stranger to this domain cannot state plainly what the tool produces.

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?

'Runs before organize_save' gives clear sequencing context, which is real usage guidance. However, there is no statement of when to skip it, whether it is mandatory before organize_save, or how it relates to the many other read siblings (read_home, list_homes, read_file).

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