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

The annotations already establish that this is a read-only, non-destructive operation. The description adds important context beyond those annotations: the payload is fictional, contains no real person, mirrors the shapes of real tools, and works without credentials. It does not discuss determinism or exact field-level return behavior, but the demo safety profile is clear.

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 sentences, each contributing distinct information about purpose, content, and the no-credential/fictional nature of the data. It is front-loaded with what the tool provides and contains no 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?

For a zero-parameter demo tool with no output schema, the description fully covers what the agent gets and why it would call this tool. No invocation details are missing.

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 there is no parameter semantics to explain. The description correctly focuses on the returned sample data rather than on nonexistent inputs.

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 states that the tool returns a fictional sample pipeline and enumerates its contents: ICP, signal definitions, pipeline stats, prospects, signals, quotes, and drafts. It clearly distinguishes itself from real-data sibling tools by emphasizing that it requires no credential and is for showing output before an account exists.

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 gives a clear use case: demonstrating what Getcleed produces before an account exists, with no credential required. It does not explicitly name alternative sibling tools such as get_icp or list_prospects for real data, nor does it state when not to use this tool.

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