MarathonGetMarathonStudents

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description's 'List' is consistent with a read-only operation. The description adds no deeper behavioral context such as pagination, result envelope, or filter semantics, but for a simple listing operation the annotations already carry the core safety profile.

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 one compact sentence that front-loads the action and resource. Every word contributes to understanding, with no repetition of the tool name and no boilerplate.

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 Filter enum values are left entirely unexplained, and the schema's descriptions are uninformative, so an agent cannot reliably choose the correct filter. There is also no output schema to clarify the return shape, and the description does not address whether MarathonId is required for a meaningful request. Annotations cover read-only safety but not the call semantics needed for correct invocation.

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%, so the baseline is 3. The description adds the high-level notion that SearchTerm and Filter correspond to search/filter behavior, but it does not explain the Filter enum values (0–5) or whether MarathonId is truly optional in practice. The schema's own 'string (optional)' and 'integer (optional)' descriptions provide little real semantic value.

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 uses a specific verb ('List') and a specific resource ('students in a marathon'), making its purpose immediately clear. It also distinguishes itself from sibling tools such as MarathonGetModerators and MarathonGetMarathonList by naming the exact entity being retrieved.

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 phrase 'List students in a marathon' gives clear context for when this tool is appropriate: whenever a marathon's student roster is needed. It does not explicitly name alternative tools for related cases, such as listing moderators or all pupils, so it stops short of full exclusion guidance.

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