list_filesystem_mediafiles

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint, and the description's 'Read' matches those. However, the description adds no behavioral context beyond the annotations, such as what the path filters, whether traversal is recursive, or what happens with a null path.

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 short and front-loaded, but it is under-specified rather than appropriately concise. The endpoint line adds some value, while the args line mostly repeats what the input schema already shows.

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 only one parameter, the description still leaves key context missing: the meaning of path, the expected resource type, and the relationship to sibling filesystem tools. The output schema and annotations exist, but the description alone is not enough for correct tool selection and invocation.

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%, so the description needed to explain the path parameter, but it only restates it as 'path: Query parameter.' This does not clarify what the path represents, what formats are accepted, or how a null default behaves.

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 says 'Read FileSystem,' which gives a verb and general resource but is vague and does not mention media files. The endpoint URL clarifies the target, but it does not distinguish this tool from siblings like list_filesystem or list_filesystem_type.

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?

No guidance is given about when to use this tool versus alternatives. The description does not explain how this differs from list_filesystem or list_filesystem_type, nor does it state any conditions or exclusions.

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