layerfs_operator_files_stats

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds only the cryptic caveat that 'physical attribution can be null' – it never explains what the diagnostics contain, what 'physical attribution' means, or what an agent should do when it is null, which matters since no output schema exists.

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?

It is a single front-loaded sentence with no filler, but its brevity stems from under-specification rather than efficiency – the second clause is opaque.

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?

For a tool with no output schema and zero-documented parameters, the description should explain the ref/path semantics and what diagnostics come back. It leaves both the inputs and the return content essentially unexplained.

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 0%: neither 'ref' nor 'path' is documented in the schema, and the description does not mention either parameter or clarify what 'ref' refers to (project? branch? workspace?). With two required parameters and no compensation anywhere, the agent is guessing.

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 'Read file storage diagnostics' is identifiable but 'diagnostics' is vague – an agent can't tell what stats are returned or how this differs from the sibling layerfs_fs_stat or layerfs_operator_store_stats. No sibling differentiation is offered.

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?

There is no guidance on when to use this versus layerfs_fs_stat or layerfs_operator_store_stats, no prerequisites, and no exclusions. The agent must infer usage from the name alone.

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