pipeline_status

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

With no annotations, the description carries the burden of behavioral disclosure. It clearly states the tool does not send a user prompt or task data, and that probe mode is restricted to provider metadata. This is strong safety-relevant behavioral transparency, though it omits other behavioral details like permissions or side effects.

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 compact and front-loaded with the main purpose. The second sentence adds necessary detail about the probe behavior without wasting words. Minor formatting quirks (backticks and line breaks) do not detract significantly.

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 two-optional-parameter tool with an output schema present, the description covers the essential safety behavior and the probe mode. However, the undocumented provider parameter and the lack of guidance relative to sibling tools leave meaningful gaps in the overall context an agent needs.

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%, so the description must compensate. It explains the semantics of probe=True clearly, but the provider parameter is left entirely undocumented. With two parameters and only one explained, the description only partially compensates for the schema's lack of documentation.

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 a clear verb and resource: 'Check pipeline readiness without sending a user prompt.' It conveys the tool's core purpose and adds a meaningful scoping constraint (no user prompt). However, it does not explicitly distinguish itself from the sibling router_status, so it falls just short of full differentiation.

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 usage-relevant context by explaining the default is local-only and that probe=True permits only a provider health/model-metadata request. This implies when the probe option would be used, but it never explicitly states when to choose this tool over alternatives like router_status or other pipeline tools.

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