list_jambonz_tools

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

No annotations provided but the description fully discloses behavior: it lists tools with their schemas. The tool is read-only and non-destructive, appropriately conveyed for a listing 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?

Three concise sentences: purpose, usage guidance, and enumeration. Front-loaded with the core action, no redundancy, every sentence adds value.

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 zero parameters and no output schema, the description is fully complete. It tells the agent what to expect (list of tools with schemas) and includes actionable advice, leaving no gaps.

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?

Input schema has zero parameters, so description's mention of listing tools with schemas adds meaningful context. It emphasizes the value of the output without needing parameter details.

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 tool's purpose: listing pre-built tools from @jambonz/tools with full parameter schemas. It uses a specific verb 'list' and resource 'pre-built tools', distinguishing it from sibling tools like get_jambonz_schema and get_sdk_example.

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 advises to check here before hand-rolling a toolHook handler, encouraging use of ready-made tools if one fits. Also lists available tools, providing clear context for when to use.

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