List all AI assistants on the Famulor account (paginated). Returns the assistant configurations including their fixed variable names.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| per_page | No |
| Name | Required | Description | Default |
|---|---|---|---|
| to | No | ||
| data | No | ||
| from | No | ||
| total | No | ||
| per_page | No | ||
| last_page | No | ||
| current_page | No | ||
| next_page_url | No | ||
| prev_page_url | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations provide readOnlyHint, idempotentHint, destructiveHint. The description adds that the tool is paginated and returns specific fields (variable names). No contradictions. However, it does not disclose how pagination works (e.g., default page size, maximum results) or any other behavioral quirks.
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?
Two sentences, front-loaded with the core purpose and key details. Every word serves a purpose. No redundancy or filler.
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 simple list operation, the description covers the essential return content (configurations, variable names) and pagination. The output schema exists, so return details are structured. It could mention authentication scoping or handling of large result sets, but overall it is adequate.
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 has 0% description coverage for parameters. The description only mentions 'paginated', which hints at the purpose of 'page' and 'per_page', but does not explicitly state their function, valid ranges, or defaults. The parameter names are self-explanatory but the description adds minimal value beyond that.
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 specifies a clear verb ('List all'), resource ('AI assistants'), scope ('on the Famulor account'), and key features ('paginated', 'returns configurations including their fixed variable names'). It effectively distinguishes from sibling tools like 'get_assistant' (singular) and 'get_outbound_assistants'.
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 for listing all assistants, but does not explicitly state when to use this over alternatives (e.g., 'get_assistant' for a single assistant) or when not to use it. The context of siblings is present but not leveraged in the description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools target distinct resources and actions clearly (e.g., create_assistant vs create_campaign). However, there is some overlap like get_outbound_assistants vs get_assistants and list_all_phone_numbers vs get_phone_numbers, causing minor ambiguity.
Tools follow a consistent verb_noun pattern with underscores (e.g., create_document, delete_label, get_voices). Only minor deviations exist, such as generate_ai_reply and list_all_phone_numbers, but overall the pattern is maintained.
With 75 tools, the server is excessively large. Although the domain is broad (assistants, calls, messaging, etc.), the number of tools makes it difficult for agents to navigate and select the correct one, reducing coherence.
The tool set covers CRUD operations for most resources, plus webhooks, AI replies, and reference data fetching. Minor gaps exist (e.g., no delete_conversation, no attach phone number to assistant), but the surface is largely comprehensive for the platform's purpose.
