fetch_asset_folders

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

With no annotations provided, the description carries full burden but provides minimal behavioral information. It mentions pagination parameters but doesn't describe the return format, whether results are sorted, what permissions are required, or any rate limits. For a read operation with zero annotation coverage, this is inadequate.

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 with zero wasted words. It's front-loaded with the core purpose ('List asset folders') followed by parameter mention. Every sentence earns its place, though the brevity comes at the cost of completeness.

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 2 parameters, 0% schema coverage, no annotations, and no output schema, the description is incomplete. It doesn't explain what 'asset folders' are in this context, what the response looks like, or provide enough context for reliable 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 schema provides no parameter documentation. The description mentions 'Optional per_page, page' which identifies the parameters but doesn't explain their purpose, valid ranges, or default values. It adds minimal semantic value beyond naming the parameters.

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 'List asset folders' clearly states the verb ('List') and resource ('asset folders'), but it's vague about scope - it doesn't specify if this lists all folders, only top-level folders, or folders with specific criteria. It distinguishes from obvious non-siblings like 'create_asset_folder' but doesn't differentiate from similar fetch tools like 'fetch_assets' or 'get_asset_folder'.

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 guidance on when to use this tool versus alternatives. There's no mention of when this should be used instead of 'get_asset_folder' (singular) or how it differs from other fetch operations. 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.