clickup_goal_get

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

With no annotations provided, the description must carry full burden for behavioral disclosure. It states the tool returns a goal object with key_results array, implying it's a read operation. However, it doesn't explicitly confirm no side effects, no state changes, or potential errors beyond the permission note in the parameter description.

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 two sentences long, each serving a purpose: the first explains what the tool does and what it returns, the second confirms the return structure. No unnecessary words.

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 tool's simplicity (one required parameter, no output schema, no nested objects or enums), the description fully covers what an agent needs to know: what action is performed, what data is returned, and how to get the input parameter.

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 single parameter goal_id is fully described in the schema. The description adds context: how to obtain it (from clickup_goal_list) and access requirements, which is valuable beyond the schema definition.

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 action 'Fetch a single ClickUp goal' and lists the data it returns (key results, owners, due date, percent-complete). It distinguishes itself from sibling tools like clickup_goal_list (which lists many goals) and clickup_goal_update (which modifies).

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 when to use: when you need detailed information about a specific goal. It also hints at where to get the goal_id (from clickup_goal_list). However, it doesn't explicitly state when not to use or mention alternatives beyond that.

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