list_group_content

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

With no annotations provided, the description carries the full burden. It successfully explains the conditional logic between `uuid` and `databaseName` parameters, but fails to disclose what 'content' entails (record objects, names, UUIDs?) or the return structure, leaving the agent uncertain about the result format since no output schema exists.

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 with zero waste. The first sentence establishes purpose immediately; the second efficiently covers both parameter interaction patterns. Every word earns its place.

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 simple 2-parameter schema with full coverage, the description is minimally adequate. However, the absence of an output schema and annotations means the description should have described the return value or read-only nature to be complete; it falls short of this expectation.

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 schema has 100% description coverage, establishing a baseline of 3. The description paraphrases the schema's logic (omitting uuid lists root, databaseName ignored when uuid provided) without adding significant semantic enrichment like example UUID formats or clarifying that 'group' refers to DEVONthink's folder-like containers.

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 verb (Lists) and resource (content of a specific group in DEVONthink). It distinguishes from siblings like `get_record_content` (which retrieves binary content of a single record) through the use of 'Lists' implying enumeration of children/items, though it doesn't explicitly differentiate from `list_smart_groups`.

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 clear guidance on parameter usage patterns (supply UUID vs omit for root, use databaseName for named database), acting as implicit usage logic. However, it lacks explicit guidance on when to use this tool versus alternatives like `search` or `get_record_by_identifier` for finding items.

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