get_member_goals

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

The description adds context beyond annotations: it notes the tool is read-only (consistent with readOnlyHint), safe to retry, has a max concurrency limit, and returns a specific error if member not found. Annotations already provided readOnlyHint and destructiveHint, so the description adds valuable behavioral details.

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 concise and well-structured, with a clear summary, usage guidance, and parameter list. A few sentences could be more logically grouped, but overall it is efficient and front-loaded with key information.

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?

Despite having only 3 parameters and no schema descriptions, the description covers authentication, rate limits, parameter details, return format, and error behavior. It is fully complete for a read-only retrieval tool with an existing output schema.

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?

Schema coverage is 0%, so the description must fully explain parameters. It does so thoroughly: list_id with format example and source, email_address with derivation note, account as optional with naming convention. This provides essential meaning beyond the schema.

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 explicitly states the verb 'Retrieve' and the resource 'Goal events' with a specific limit of 50. It clearly distinguishes from sibling tools like get_member_activity and search_members, ensuring the agent knows when to use this tool.

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 provides explicit when-to-use guidance ('Use to see which tracked website Goals...'), recommends alternatives (get_member_activity for broader activity, search_members to locate member first), and includes authentication and rate limit info (API key, max 10 concurrent requests).

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