run_ingestion

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

No annotations provided, so description carries full burden. It discloses that the operation fetches, analyzes, notifies, and may take several minutes. However, it does not specify side effects like data mutation, permission requirements, or cancellability, which are important for a pipeline run.

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 extremely concise with two sentences plus a one-sentence warning. Front-loaded with the primary action, no redundant information, and easy to parse. Every sentence contributes useful information.

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 the tool has an output schema, return values need not be explained. The description covers the core functionality and behavior (time consumption). However, it could be more complete by mentioning error handling or impact on existing data, but overall sufficient for a pipeline tool.

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 description coverage is 0%, but the description explains the single parameter profile_id: it specifies the profile to run for, or if null, all active profiles. This adds meaningful context beyond the schema's type definition, though format details are not provided.

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 runs the data ingestion pipeline, detailing actions: fetches, analyzes, notifies. It uses a specific verb 'run' and resource 'data ingestion pipeline,' effectively distinguishing it from sibling tools like analyze_apartment or search_apartments.

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 implies usage: run ingestion to process apartments for a profile or all profiles. It mentions the time-consuming nature but lacks explicit guidance on when to use versus alternatives or when not to use. No exclusions or alternative tool references.

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