List the demo book of business — the fictional contacts Centric is tracking for demo RM Marcus Johnson. Returns name, title, company, R/Y/G health, and days since last touch. Start here.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description fully describes the return payload (name, title, company, R/Y/G health, days since last touch) and clarifies the data is fictional. As a list operation, it implies read-only behavior, though it doesn't explicitly state safety or side-effect absence, which is minimal for this type.
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 only, with the action verb leading, return fields listed, and a clear call-to-action 'Start here.' No wasted words; every part 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?
For a simple, parameterless list tool, the description covers purpose, data scope, return fields, and usage context. It is complete on its own, and the lack of an output schema is offset by listing the return fields explicitly.
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, and the description appropriately does not discuss any. With no parameters to clarify, the baseline of 4 applies and no additional semantic explanation is needed.
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?
Clearly states the tool lists the demo book of business for demo RM Marcus Johnson, specifying the fictional contacts context. The verb 'List' and resource 'demo book of business' are specific, and it distinguishes itself from sibling tools like get_contact_profile or get_radar.
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 includes 'Start here,' which implicitly positions this as the initial tool to use for the demo book, providing context on when to use it. It lacks explicit exclusions or alternative tool names, but the forward-looking hint is useful.
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.
The tools are mostly distinct: list_demo_contacts retrieves the book of business, get_contact_profile provides the full profile, get_radar returns the radar widget data, draft_as generates outreach, and demo_temperature_check is an interactive walkthrough. However, brief_me and get_contact_profile both include summaries and cadence notes, which could cause initial confusion even though brief_me is specifically for pre-interaction prep.
All tool names use lowercase with underscores, but the verb conventions vary: get_ and list_ are used for retrieval, while brief_me, draft_as, and demo_temperature_check use imperative or verb-particle forms. This is not chaotic, but lacks a uniform verb_noun pattern.
With six tools, the server is well-scoped for a demo application. Each tool covers a distinct aspect of the demo workflow—listing contacts, viewing profiles, inspecting radar graphs, generating briefs, drafting messages, and simulating temperature checks—without redundancy or bloat.
The tool set thoroughly covers the core capabilities of the Centric demo: viewing contact lists, profiles, radar visualizations, interactive briefs, drafting, and temperature check loops. The intentional demo-only nature (no send/update) means no obvious workflow dead ends exist for the stated purpose.