list_goals

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

With no annotations provided, the description bears full responsibility for disclosing behavior. It states the tool lists goals, which implies read-only operation, but it does not explicitly confirm no destructive side effects, nor does it mention pagination, rate limits, or other behavioral traits. The description is too sparse to adequately inform an AI agent.

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 a single sentence that conveys the essential purpose without unnecessary words. It is well-formed and front-loaded, but could be slightly expanded to include pagination context without becoming verbose.

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?

Although the tool has an output schema (reducing the need to describe return values), the description still lacks critical context such as pagination behavior, default ordering, and any limitations. For a list tool with limit and offset parameters, the absence of these details makes the description incomplete for an agent to use effectively.

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 has 0% description coverage for its parameters (limit and offset). The description adds no information about these parameters, leaving the agent to infer their meaning from the schema properties only. This fails to compensate for the schema's lack of descriptions.

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 clearly states the verb 'List' and the resource 'goals', and explains that goals are conversion events tied to automations with concrete examples. This distinguishes the tool from siblings that deal with contacts, deals, etc., making its purpose unambiguous.

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 implies the tool should be used when needing to retrieve conversion events tied to automations, but it provides no explicit guidance on when to use this tool versus alternatives, nor does it mention when not to use it. Since there are no sibling tools with similar functionality, the lack of exclusions is less critical, but the guidance remains implicit.

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