list_deeptutor_sessions

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds minimal behavioral context ('historical learning data') but does not mention pagination, ordering, or other runtime behavior beyond what the schema implies. No contradiction 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 a single concise sentence, front-loaded with the verb and object. It avoids fluff, but could have included usage guidance without becoming verbose. It is effective though slightly under-specified for a tool with several siblings.

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 nature of the tool, the schema covers parameters and an output schema exists, so return format is not needed. However, the description lacks any indication of when to prefer this over related tools or details like the 'all_workspaces' behavior, which the schema describes but the description does not contextualize. Overall, it is minimally adequate.

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?

Schema description coverage is 100%, with clear descriptions for 'limit', 'offset', and 'all_workspaces'. The tool description adds no extra detail about parameters, so the baseline of 3 is appropriate given the schema already handles parameter documentation.

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 'DeepTutor conversation records' with the purpose of 'historical learning data'. The verb 'List' and the specific resource are unambiguous, and it is clearly distinct from sibling tools like 'get_deeptutor_session' which fetches a single session.

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?

No guidance is given on when to use this tool versus alternatives such as 'get_deeptutor_session' or other listing tools. The description does not mention exclusions, conditions, or alternative selection criteria, leaving the agent to infer usage from the name alone.

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