Get top-level categories

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description adds only the 'top-level' scoping notion; it says nothing about whether children are included, ordering, or what happens if the team has no categories.

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 well-formed sentence with the resource and scope front-loaded and no filler. It is efficient, though it is arguably under-specified rather than truly concise.

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, closed-world read tool with no output schema, the description is minimally sufficient: the agent knows it lists top-level categories for a team. It omits the shape of the result (flat list vs. tree) and how the empty-default teamName resolves, which would help given the schema marks it 'required' but gives it a default.

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% for the single teamName parameter, including the pointer to esa_get_teams, so the schema carries the full semantic load. The description contributes nothing about the parameter, which is the expected baseline when the schema is complete.

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 states a specific verb and resource ('Retrieves all top-level categories') with a clear scope qualifier ('top-level') and the owning entity ('for a team'). It does not, however, differentiate itself from near-name siblings like esa_get_categories or esa_get_all_category_paths, leaving the agent to guess which one returns the hierarchy.

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?

There is no guidance in the description about when to use this tool versus esa_get_categories, esa_get_all_category_paths, or the team-scoped siblings. The only routing hint ('Use esa_get_teams first') lives in the schema, not the description, and no prerequisites or exclusions are stated.

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