MarathonGetMarathonList

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds that the operation is paginated and supports search/folder filtering, which is useful behavioral context not present in annotations. However, it doesn't disclose return format, default page size, or ordering, so it adds only modest 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, front-loaded sentence. Every part adds information: the action, the resource, and the key capabilities. No filler.

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 simple read-only list operation with four optional parameters, the description covers the main behavioral dimensions (paginated, search, folder filter) and the schema covers the parameters. It doesn't describe the response shape, but 'List marathons' implies returning marathon entities, and there is no output schema to document.

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?

Although schema coverage is 100%, each parameter's description is tautological ('integer (optional)', 'string (optional)'). The tool description compensates by mapping SearchTerm to 'search' and FolderId to 'folder filter', and pageSkip/pageTake to 'paginated', giving the agent actual semantic understanding of the parameters.

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?

States a specific verb ('List') and resource ('marathons'), with modifiers (paginated, search, folder filter). The resource is distinct from siblings like MarathonGetMarathonStudents or MarathonGetModerators, though it does not explicitly name them.

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 explicit when-to-use or alternatives are mentioned. The only guidance is implied: use when you need to list marathons. It doesn't explain when to prefer this over MarathonGetMarathonStudents or other list tools, nor when to use the search/folder filter.

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