Get Pipeline Item

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

No annotations are provided, so the description carries the transparency burden. It clearly signals a read operation via 'Retrieve' and adds a useful behavioral note that search_pipeline_items returns the same full data, but it does not disclose output format, error handling, or ID formatting constraints. This is adequate but not rich.

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 short sentences. The first states the core purpose, and the subsequent sentences give usage guidance. The note is useful but slightly overlaps with the previous sentence ('need the record' vs. 'have an ID but not the data'), yet overall it is tight and well-structured.

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 one-parameter read operation with no output schema, the description covers what, when, and when not to use the tool. It does not explicitly describe return values, but the verb 'Retrieve' and the note about search returning full data imply the record is returned, making this nearly complete.

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 input schema already documents pipeline_item_id as 'The PipelineItemId to retrieve' with 100% coverage. The description's 'by ID' adds no new semantic meaning beyond the schema, so the baseline 3 for high schema coverage applies.

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 opens with a specific verb and resource: 'Retrieve a single pipeline item by ID.' It clearly defines the tool's scope and distinguishes it from the sibling search_pipeline_items by noting when the ID-based lookup is appropriate.

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 explicitly states when to use the tool ('when you already have a PipelineItemId and need the record') and when not to use it ('only use get_pipeline_item when you have an ID but not the data'), and it names the alternative search_pipeline_items.

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