things_list_projects

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

With no annotations, the description carries the full behavioral burden. It usefully discloses a beta status and the returned fields, but says nothing about read-only safety, result volume, ordering, or pagination. It also implies an area filter without explaining how it is supplied.

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?

One compact sentence that front-loads the beta marker and the core action. The trailing field list is dense but earns its place given there is no output schema; phrasing around the area clause is slightly ambiguous.

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?

For a simple zero-parameter list tool this is close to adequate: the returned field list compensates for the missing output schema and the beta flag warns of instability. The unresolved question of how the area filter is specified leaves a gap an agent cannot close from the definition alone.

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 tool takes zero parameters, which would normally set a baseline of 4. However, the description's claim that it lists 'those of one area' introduces a scoping input that the empty schema does not expose, creating ambiguity about how area selection actually happens.

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?

States a specific verb and resource (lists open projects in Things 3) and briefly scopes by area. It does not explicitly distinguish itself from close siblings like things_list_areas or things_list_todos, so an agent infers the distinction from the resource nouns alone.

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?

There is no when-to-use or when-not-to-use guidance and no routing to alternatives such as things_list_areas or things_list_todos. The only implicit cue is the phrase 'open projects', which hints at filtering by completion status but is not explained.

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