layerfs_status

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely non-obvious behavioral context: that this read will not lazily initialize project data nor kick off a preparation attempt — something an agent could easily assume a status call does. It does not describe the shape of the response, but the core behavioral caveat is well disclosed.

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 front-loaded sentences with no filler: the first enumerates what is reported, the second immediately qualifies the side-effect boundary. Slightly dense enumeration of four report areas in one sentence, but nothing that fails to earn its place.

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 zero parameters, rich annotations, and no output schema, the description carries most of the burden and does cover what the call reports plus its key non-effect. The only shortfall is not clarifying its relationship to the overlapping workspace_status / project_progress siblings, which would help an agent pick 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 tool takes zero parameters with additionalProperties=false, so there is nothing for the description to disambiguate. The baseline for a parameterless tool applies; no parameter-level gaps exist.

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 names a concrete verb ('Check') and enumerates the resources it reports on: configuration, runtime preparation progress, pinned upstream revision, and exposed methods. That is far more specific than a tautology. It stops short of distinguishing this tool from closely named siblings such as layerfs_workspace_status and layerfs_operator_project_progress, leaving overlap ambiguity.

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 sentence 'This read does not initialize project data or trigger another preparation attempt' implies the safe, side-effect-free context in which to call it, which is a useful usage signal. However, no alternative is named — it never says to use layerfs_project_init to actually trigger preparation or layerfs_operator_project_progress for per-project detail, so the agent must infer routing among several overlapping status-style siblings.

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