native_list_sidecars

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

With no annotations provided, the description carries the full burden of behavioral disclosure. The verb 'List' conveys read-only behavior, and the parenthetical adds detail about what content is returned. However, it does not explicitly state that there are no side effects or permissions needed, though these are generally inferred for a list operation.

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, front-loaded sentence with no wasted words. The parenthetical efficiently conveys the content scope without unnecessary elaboration.

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 simple list tool with no parameters and no output schema, the description provides adequate completeness by naming the location (native/) and the categories of items listed. It does not explain potential error conditions or the exact return format, but these are less critical for a straightforward listing operation.

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 tool has zero parameters, so schema coverage is effectively 100% and no parameter documentation is needed. The baseline of 4 applies, and the description adds no parameter information since there are none.

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 the verb 'List' and the specific resource 'native DLL/EXE kits under native/', with a parenthetical enumerating content categories (paths, files, proxies, tools, tool_guide). This distinguishes it from sibling listing tools like gal_list_dir, which targets a different directory.

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 when to use the tool (when you need to list native sidecars) but provides no explicit or-when-not guidance or alternatives. It does not mention exclusions or compare with sibling tools like native_deploy or native_run.

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