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.