analytics_goals_list

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

The annotation readOnlyHint=true already indicates a read-only operation. The description adds no additional behavioral traits beyond 'list', so it provides minimal added value. No mention of pagination, rate limits, or authentication requirements.

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 Python docstring format with Args and Returns, which is clear but somewhat verbose. The first line is efficient, but the block format could be condensed. It is not overly long but not maximally concise.

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?

Given the existence of an output schema (declared but not shown), the description's 'Goals list with metadata' is adequate for a simple list tool. However, it lacks details on metadata fields, error handling, or pagination behavior, which would be helpful.

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 0% schema description coverage, the description compensates by explaining each parameter: website_id as 'Website/App UUID', limit as 'maximum number of rows to return' with defaults, and offset similarly. This adds significant meaning beyond the schema's minimal type/title fields.

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 'List all goals for a website', using a specific verb and resource. This distinguishes it from siblings like analytics_goals_get (single goal) and other list tools.

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 is provided on when to use this tool vs alternatives. The sibling list includes analytics_goals_get and analytics_goals_list, but the description does not mention these or provide any selection criteria.

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