Get Goal Completions

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states that the tool 'gets' data, without explaining request behavior, pagination, defaults, or response details. It does not mention how filters interact or any caveats, leaving significant ambiguity for a 23-parameter tool.

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 one concise sentence, front-loaded with the primary action ('Get custom goal completion data'). Every word adds value, with no filler or redundancy.

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 description names the output fields, it does not provide broader context such as required filters, timezone defaults, or pagination behavior. Given the tool's 23 parameters and no output schema, a bit more detail about the response shape or usage notes would increase completeness, but the core purpose is clear.

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 schema covers 100% of the parameters with descriptions, so the baseline is 3. The tool description adds no additional meaning about the parameters themselves, merely naming the output fields. It does not need to compensate since the schema is thorough.

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 tool retrieves 'custom goal completion data' with specific output fields (goal name, completions, unique visitors). This distinguishes it from sibling analytics tools like get_pages or get_browsers, which focus on other metrics.

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 this tool is for goal completion metrics, but it does not explicitly state when to use it over alternatives or mention any exclusions. No sibling tools or alternative contexts are referenced, so the guidance is mostly implicit.

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