ingest_pendo_payload

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

With no annotations, the description carries the burden. It discloses normalization and merging behavior, explains how default kind is applied and overridden by per-item evidence. Missing details on merge semantics (e.g., overwrite vs. append) but the core behavior is well described.

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 dense but focused. It front-loads the main idea and uses examples to clarify. The phrase 'EASIEST' is slightly promotional but the content is informative without being bloated.

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 tool with no output schema and no annotations, the description covers input formats, parameter behavior, and merge logic well. It does not describe return values or error handling, but the primary ingest purpose is adequately addressed.

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 coverage is 100%, but the description adds meaningful context: explains that `kind` is a default for items lacking kind evidence, `payload` can be array/wrapper/JSON string, and `appId` is stamped. This goes beyond the schema's static descriptions.

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's function: ingest raw Pendo MCP tool results and normalize/merge them into the ontology. It enumerates specific source tools and input formats, and the distinction from siblings like 'sync_from_pendo' is implicit by focusing on raw payload ingestion.

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?

Provides explicit usage context: pass raw Pendo MCP results, and indicates when `kind` is required (for product areas and segments). It does not explicitly contrast with alternative tools like sync_from_pendo, but the examples and instructions give clear practical guidance.

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