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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds only the underlying endpoint (GET /pipeline-status), with no mention of pagination behavior or result ordering, so it contributes little beyond structured data.

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?

Two short sentences with the resource named first, which is front-loaded and efficient. It is close to minimal, though the endpoint mention is arguably redundant with the structured metadata.

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 paginated list tool with full schema coverage and annotations, the description covers the core purpose but omits any hint of return shape or ordering. With no output schema present, the description could reasonably say more about what a pipeline status record looks like.

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 100%, and the page/limit semantics including defaults and the next_page handoff are fully documented in the schema. The description adds nothing about parameters, which is acceptable at full coverage but provides no extra value.

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 specific verb+resource ("List customer pipeline statuses"), which is clearer than the title alone. However, it does not distinguish itself from nearby siblings like fieldpulse_list_job_status_workflows, fieldpulse_list_job_workflow_statuses, or fieldpulse_list_lead_sources, leaving the agent to infer the difference.

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?

No guidance on when to use this tool versus alternatives, and no exclusions or prerequisites are given. The agent must infer usage purely from the tool name and the ambiguous phrase "pipeline statuses."

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