Get IELTS dashboard data

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

Annotations provide readOnlyHint=true and destructiveHint=false, largely covering the safety profile. The description adds scope context ('local session and target data') beyond annotations. It doesn't disclose whether data requires initialization or whether an empty result is possible if no session exists, but with annotations covering safety, a mid score is appropriate.

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?

Single, efficient sentence. Zero wasted words, clearly front-loaded with the resource type and purpose. Nothing extraneous.

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 is a simple no-parameter read operation with strong annotations (readOnlyHint, destructiveHint) and an output schema present. For a zero-parameter retrieval tool, the description adequately captures scope. Could note behavior when no data exists yet, but the output schema likely handles structure, keeping this mostly complete.

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 tool has 0 parameters and schema coverage is 100%, so the baseline is 4. With no parameters to document, the description doesn't need to add parameter semantics. There is nothing missing here since there are no params.

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?

Clear verb+resource: 'Return the learner's local session and target data' specifies what data is retrieved. The purpose for a dashboard/progress summary is stated. It doesn't explicitly distinguish from siblings like get_training_context, but the resource ('local session and target data') is reasonably 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 when building a dashboard or progress summary. It doesn't name alternatives or exclusions, though sibling tools like open_dashboard could overlap. The context is implied rather than explicit, and no when-not-to-use guidance is given.

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