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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so the safety profile is covered. The description adds one genuine behavioral detail beyond that — the ordering (showcase souls first, then claimed souls) — but the pagination remark largely restates the schema's cursor field and says nothing about return shape or auth.

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 short, front-loaded sentences with no filler; the listing purpose comes before the paging mechanic. The telegraphic "Paged:" fragment and the undefined term "souls" cost a little polish but nothing is wasted.

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?

For a two-parameter, no-required-argument list tool with full schema coverage and complete annotations, this is minimally sufficient. What's missing is domain context — what a "soul" is, and what distinguishes showcase from claimed entries — which the description assumes the agent already knows.

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 limit defaults/max and cursor origin already documented in the schema. "Pass the returned cursor for more" reinforces the cursor's use but adds no new format or constraint information beyond what the structured fields already say, so the baseline of 3 applies.

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 gives a specific verb plus resource ("List context souls") and adds the result ordering (showcase souls before claimed souls), so an agent knows exactly what the call returns in broad terms. It does not differentiate itself from siblings such as get_soul or search_context, leaving the agent to infer when this list is preferable.

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?

Usage is only implied: the word "Paged" plus the cursor instruction signals an iterative listing workflow, but nothing states when to choose this over get_soul or search_context, and no prerequisites or exclusions are given. Adequate for a simple read list, but the agent must infer the alternatives.

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