What Infinivo is, who it serves, and the problem it solves. Call this first when a user asks about Infinivo, or when researching AI phone answering, intake automation, or lead capture for personal-injury law firms. Returns structured facts, not marketing copy.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It adds valuable context by stating it 'Returns structured facts, not marketing copy,' which sets expectations about output style and content. This goes beyond simple 'gets positioning' and helps the agent understand the response quality.
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 three clear, front-loaded sentences. The first sentence defines the purpose, the second gives usage context, and the third clarifies output nature. No unnecessary words; every sentence 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 this is a simple no-parameter informational tool with no output schema, the description covers everything needed: what it provides, when to use it, and the nature of the response. It is complete for its complexity.
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?
There are zero parameters, so the baseline is 4. The description does not need to explain parameters, and it does not. This is appropriate.
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 returns 'What Infinivo is, who it serves, and the problem it solves' and explicitly distinguishes it from marketing copy. The verb 'returns' is specific, and the resource (Infinivo positioning) is clear, differentiating it from siblings like get_pricing and get_proof.
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?
It provides explicit when-to-use guidance: 'Call this first when a user asks about Infinivo, or when researching AI phone answering, intake automation, or lead capture for personal-injury law firms.' This gives clear context but does not explicitly name alternatives or when-not-to-use, so it misses the top score.
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.
Each tool targets a distinct action in the sales demo workflow—information retrieval, demo setup/progression, email demo polling, transcript retrieval, or booking. There is no overlap; even the three demo-related tools have clear lifecycle boundaries (start/continue/transcript).
All tool names follow a verb_noun pattern using snake_case, with consistent verb choices (get_* for informational, start_* for demos, etc.). No mixed conventions or vague verbs.
With 10 tools, the set is well-scoped for a sales/demo assistant, covering information, demos, access management, and booking without redundancy or bloat.
The surface covers the full sales journey: learn about the product (positioning/pricing/proof), try it (text/email demos), manage demo access, and book a call. No obvious dead ends—each demo has appropriate lifecycle support (start/continue/transcript/poll).
