list_asset_files

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

No annotations exist, so the description carries full burden for behavioral disclosure. It only states the action without detailing what the tool does beyond listing—e.g., whether it returns paths or IDs, if it is recursive, or if it requires graph context. This leaves significant ambiguity for an AI agent.

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 a single sentence that efficiently conveys the tool's purpose with no redundant words. It is front-loaded with the verb and resource.

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?

Given the simple nature of a list tool with one optional parameter and no output schema, the description is mostly adequate. However, it lacks context on what constitutes 'asset files,' how the list is structured, and how this relates to sibling tools like 'open_asset' or 'make_asset_url'. This leaves some gaps for an agent.

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 schema has one parameter 'exts' with no description and 0% coverage. The description adds that it is for filtering by file extension, which provides meaning beyond the schema. However, it does not specify the expected format (e.g., with or without dot).

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?

Description clearly states verb 'List', resource 'asset files', and scope 'in the current graph'. It also mentions optional filtering by extension, which is specific and distinguishes this tool from sibling tools that deal with blocks, tags, or pages.

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 implies usage for listing asset files with optional filtering, but provides no explicit guidance on when to use this tool versus alternatives like 'open_asset' or 'make_asset_url'. No prerequisites or exclusions are mentioned.

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