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

Annotations already declare readOnly, idempotent, non-destructive, and non-open-world, so safety is covered. The description adds return-content context (tutorial counts, sample articles) which is useful given no output schema, but says nothing about pagination beyond limit, rate limits, or how large the section catalog is.

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?

One tightly written sentence that front-loads the default mode and appends the conditional mode. No filler, nothing redundant.

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?

Both invocation modes, the two parameters, and the shape of the primary return (counts and samples) are covered without an output schema. Minor gaps remain around pagination limits and what 'sample articles' contains, but nothing blocks a correct call.

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% — limit's default/max and section's slug examples are fully documented in the schema. The description adds no syntax, format, or example detail beyond that, so the baseline 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?

States a specific verb (list) and resource (topic sections / tutorials within a section) with the exact site named. The dual-mode behavior ('all sections with tutorial counts and sample articles' vs 'tutorials inside a specific section') lets an agent distinguish it from get_tutorial and search_tutorials without opening any schema.

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?

Sets a clear condition for each mode: omit section to browse the catalog, supply section to drill in. It doesn't name alternatives or state exclusions (e.g., 'use search_tutorials when you know keywords'), so it stops short of full when-not guidance.

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