list_funcs

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

No annotations provided, so description carries full burden. Warns about blocking behavior and scalability. Could also mention default pagination limits or glob pattern syntax.

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?

Remarkably concise: two sentences pack purpose, warning, and usage advice. Front-loaded with critical warning. No wasted words.

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?

Covers key performance and pagination guidelines. Output schema exists, so return value details are handled. Could still note that instance_id is required and that queries can be string/single object/array.

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 coverage is 100%, so baseline 3. Description adds context about count=0 danger but doesn't explain offset/count defaults or glob pattern flattening.

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?

Starts with clear verb+resource 'List functions'. Immediately provides critical performance context with a WARNING. Distinguishes from sibling tools by emphasizing pagination and glob filtering for large binaries.

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?

Explicitly warns about blocking main thread and suggests count/offset pagination for large binaries. Also advises against count=0 with glob filters. Lacks comparison with siblings like lookup_funcs or export_funcs.

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