list_goals

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

Since no annotations are provided, the description bears full responsibility. It explicitly states it lists all sessions and is sorted, implying a read-only, non-destructive operation. It does not disclose any side effects, which is appropriate for a list 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 a single sentence that front-loads the version and action. It is concise with no redundant information; every part adds value.

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 no parameters and a simple listing functionality, the description adequately defines the tool. It mentions return fields and sorting. However, it does not specify if there is pagination or a maximum number of results, which could be relevant for a list-all tool.

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?

There are no parameters, so the schema coverage is trivially 100%. The description adds no parameter information, but none is needed. The baseline for 0 parameters is 4.

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 it lists all Goal Sessions and specifies the returned fields (goal_id, title, status, subgoal counts, last update time). It uses the verb 'list' and the resource 'Goal Sessions', distinguishing it from sibling tools like read_goal (single goal) and create_goal.

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 retrieving an overview of all goal sessions, but does not explicitly mention when to use alternatives (e.g., read_goal for a specific goal). There is no guidance on exclusions or context for when not to use it.

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