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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered and the description is exempt from carrying that burden. What it adds is limited to the ICP-ID prerequisite for the account pipeline, which largely restates the schema's own conditional ('Required when entity is account'), and it says nothing about whether results are static config vs. account-mutable state.

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 sentences, zero filler, with the return contents front-loaded before the conditional prerequisite. Nothing is repeated and nothing extraneous is included.

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 nested-schema, single-parameter tool with no output schema, the description does cover what comes back at a category level. But the unaddressed pipeline_id filter and the absence of any tie-breaker versus getPipeline leave gaps an agent would have to guess through.

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?

With schema description coverage at 0% for a nested object, the description does real work by naming the three permissible entity values and flagging the ICP-ID requirement. However, pipeline_id is never mentioned, so the agent gets no hint about what that optional filter narrows or whether omitting it returns all pipelines.

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?

States a specific verb and resource ('Returns the stages, stage categories and milestone mappings') and scopes it across the three pipeline entity types, so the agent knows exactly what it retrieves. It does not differentiate itself from the sibling getPipeline, nor from listPipelineContacts/getDealSummaries, leaving ambiguity about which pipeline tool to pick.

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?

Usage is only implied by the content list; there is no explicit 'use this when...' or 'use getPipeline instead if...' statement despite a very close sibling name. The one piece of real guidance — that the account pipeline needs an ICP ID — is a useful prerequisite, but it is framed as a fact rather than a routing rule.

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