dj_getRecentSessions

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

No annotations are provided, so the description must explain behavior. It discloses the configuration requirement (db_path) and the data source, but does not describe return format, error handling, or whether it is read-only (implied by 'get'). This is partial disclosure.

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?

Two sentences with no filler; the verb and resource appear immediately. The prerequisite sentence adds necessary context.

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 is acceptable for a simple read tool but omits the meaning of the 'days' parameter and the structure of returned data. There is no output schema, so these gaps leave the agent to infer.

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 one parameter 'days' with no description, and the description does not mention it. With 0% schema description coverage, the description fails to compensate by explaining what 'days' controls or how it relates to 'recent'.

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 a specific verb ('Get'), resource ('recent DJ sessions'), and source ('Rekordbox history'), which differentiates it from sibling tools like dj_getSessionTracks (which retrieves tracks within sessions) and dj_getHistoryStats (which computes statistics).

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 gives a prerequisite ('Requires rekordbox.db_path configured') but does not explicitly state when to use this over alternatives such as dj_getHistoryStats or dj_getSessionTracks. Usage must be inferred from the tool name and sibling names.

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