List IELTS practice history

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

Annotations declare readOnlyHint=true and destructiveHint=false, so the safety profile is already established. The description adds the 'locally saved' scoping detail, clarifying that sessions are stored locally rather than cloud-based. However, it doesn't describe return format, ordering, or pagination behavior. The description adds modest value beyond annotations but not rich context.

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?

A single concise sentence that states the action clearly without wasted words. It names the verb (list), resource (recent locally saved IELTS speaking sessions), and purpose (for review or optional retraining). Efficient and well-structured.

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 tool has only one parameter already fully documented in the schema (limit with min/max/default), a readOnly annotation, and an output schema. For such a simple listing tool, the description covers the essential intent. The purpose statement ('for review or optional retraining') adds useful context for when the agent might want this. Adequate completeness for a low-complexity tool.

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 0%, meaning the description itself contains no parameter documentation. However, the single parameter 'limit' is fully self-documenting via the schema (integer, default 10, min 1, max 50) — its semantics are obvious. With only 1 param and the description noting 'recent' sessions (implying ordered output), the parameter meaning is clear without additional explanation. No meaningful gap exists.

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?

'List recent locally saved IELTS speaking sessions' uses a specific verb (list) plus a clear resource (IELTS speaking sessions) and a scoping modifier (recent, locally saved). The purpose statement 'for review or optional retraining' adds valuable intent context. It distinguishes from siblings like get_dashboard_data (which aggregates different data) and get_training_context (training-specific). Clear and specific.

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 use cases ('for review or optional retraining') but does not explicitly distinguish when to use this tool versus siblings like get_dashboard_data, save_session_review, or set_training_selection. No when-not-to-use guidance or alternative recommendations are provided. Some context is implied via the purpose phrase, but explicit comparison to alternatives is absent.

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