list_stdlib_modules

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

No annotations provided, but the description discloses that no trace needs to be loaded and warns about potential module unavailability with custom binaries. It implies read-only operation. Lacks explicit idempotency statement but adequately covers behavioral context.

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 moderately long but well-structured with clear sections. Each sentence adds value. Slightly verbose in the usage hint, but overall efficient and front-loaded.

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?

Despite no output schema, the description fully explains the return format, use cases, and potential pitfalls (custom binary). It also provides next steps (execute_sql with INCLUDE). No gaps given the tool's simplicity.

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?

No parameters, schema coverage 100%. The description explicitly states 'Parameters: none,' which adds minimal value beyond the schema. Baseline 3 is appropriate.

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 a curated set of PerfettoSQL stdlib modules' and specifies the return format (JSON array with module, domain, views, description, usage). It distinguishes itself from siblings by noting it is not for all modules and that it should be called before load_trace.

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?

Explicit 'Use when' and 'Don't use for' sections provide clear context. It recommends calling before load_trace and directs users to the exhaustive list. Alternatives (execute_sql, list_table_structure) are mentioned in context.

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