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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the full safety profile is covered structurally. The only extra signal the description offers is the word 'connected', hinting that a HubSpot integration must be linked, but this is not stated as an explicit prerequisite and adds little beyond the 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?

It is a single short fragment with no wasted words, but it is so terse that it reads as under-specification rather than disciplined conciseness — there is no front-loaded statement of the action being performed.

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?

An output schema exists and there are no parameters, so the description does not need to explain return values or inputs. However, for a list tool with no usage guidance, the definition is only minimally sufficient — it never states what the tool returns or when it should be used.

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 tool takes zero parameters and the schema is fully described, so the baseline of 4 applies. There is nothing parameter-related the description could or should clarify.

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 phrase names a specific resource ('the connected HubSpot account's Deal pipelines and stages'), which is clearer than the bare name, but it is a noun fragment with no verb — the agent must infer the 'list' action from the tool name/title. It does implicitly distinguish itself from sibling fillo_hubspot_properties (which concerns properties), so it is adequate but not explicit.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as fillo_hubspot_properties or fillo_get_integration. The agent is left to infer that this should be called before mapping deals to stages.

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