bookshelf_list_filesystem_mediafiles

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

The readOnlyHint annotation already signals this is a safe read operation, but the description adds no extra behavioral context. It doesn't mention return format, pagination, or how the path parameter affects results, leaving the agent with only the schema and hint to infer behavior.

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 extremely concise, using only two short sentences to convey the core action and parameter list. Every word serves a purpose, with no filler or redundant information.

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?

Although this is a simple tool with one parameter and an output schema, the description lacks crucial context about the path parameter's semantics and how this tool differs from other filesystem listing tools. The agent has to guess what 'mediafiles' encompasses and how to appropriately set the path, making the description incomplete for effective use.

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?

With schema description coverage at 0%, the description was expected to explain the 'path' parameter meaning beyond its name. It merely restates 'Query params: path' without describing what the path represents (e.g., absolute/relative path), its format, or how it filters results. This adds no value over the input schema.

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 clearly states 'List filesystem mediafiles' with a specific verb and resource, indicating a read operation on media files. Although it doesn't explicitly differentiate from the sibling 'bookshelf_list_filesystem', the term 'mediafiles' narrows the scope, making the purpose reasonably distinct.

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 description provides no information on when to use this tool versus alternatives like 'bookshelf_list_filesystem' or 'bookshelf_list_filesystem_type'. It only mentions 'Query params: path', which gives a hint about the parameter but not the appropriate usage context or exclusions.

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