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

While annotations confirm it is read-only, the description adds crucial behavioral details by specifying the exact data returned: ID, name, and record count. This informs the agent about the structure of the expected output.

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, powerful sentence that packs all necessary information—resource, action, and output fields—with zero extraneous wording. It is perfectly balanced between brevity and 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?

Given the tool is simple (no inputs, read-only), the description is fully complete. It informs the agent precisely what information it will receive upon successful execution.

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?

Because there are no input parameters, the description adds semantic value by defining the scope of the listing—specifically, the apps that 'this key can open.' This context is vital for the agent's operational understanding.

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 uses specific terminology ('Bionic Forms apps') and clearly defines the action (list), ensuring the AI distinguishes it from sibling tools like get_record or list_records. It leaves no ambiguity regarding the resource being accessed.

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?

Since the tool requires no input parameters, complex usage guidelines (like when to use versus alternatives) are largely unnecessary. The inherent specificity of listing apps versus listing records provides sufficient contextual usage guidance.

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