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

With no annotations provided, the description takes on the burden of disclosing behavioral traits. It explicitly states 'Read-only,' which is a key safety characteristic, and the function name 'list' reinforces the non-mutating nature. However, it doesn't add details about return format or any side effects, though for a list operation this is relatively satisfactory.

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 is front-loaded with the action, includes the underlying function name for precision, and contains no redundancy. Every word earns its place.

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 that the tool has no parameters and an output schema is present, the description provides complete context: what it does, its read-only nature, and its identity. Nothing additional is necessary for an agent to select and invoke it correctly.

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 the description does not need to explain parameter semantics. The baseline for zero-parameter tools is 4, and the description appropriately avoids adding unnecessary parameter information.

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 action ('List functions') and the resource ('deployed to Animica Studio'), and also includes the underlying function call 'aicf.fn.list' for additional disambiguation. This is distinct from sibling tools which cover AI, chain, quantum, and pool functionality.

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—it's a listing tool for deployed functions—but provides no explicit guidance on when to use it versus alternatives, nor any exclusions. For a simple list operation, the context is fairly clear, but the guidance is minimal.

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