dt3_selection

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

The annotations already cover read-only, idempotent, and non-destructive behavior. The description adds the detail of filtering by access policy, which is a behavioral nuance not present in the annotations. This extra information enhances transparency beyond the annotations.

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, concise sentence that conveys the core functionality without unnecessary detail. It is well-structured and directly to the point.

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?

The description adequately conveys that the tool returns metadata for the current selection, filtered by access policy. It does not elaborate on the output format, but given the existence of an output schema and the simplicity of the operation, it is reasonably complete. Slight improvement could clarify pagination behavior, but it is not essential.

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 input schema includes limit and offset with defaults and bounds but no descriptions. The tool description does not explain these parameters or their purpose. As schema coverage is 0%, the description fails to compensate, leaving parameters ambiguous.

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 tool reads metadata for the current DEVONthink selection, with a specific filtering criterion (access policy). This distinguishes it from sibling tools like dt3_search or dt3_get_record, which handle different operations.

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 usage for retrieving metadata of the currently selected items, but it does not explicitly contrast with alternatives such as dt3_get_record or dt3_search, nor does it state when not to use it. No explicit when/when-not guidance is provided.

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