List Sections

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

With no annotations, the description carries the behavioral burden. 'List' implies a non-mutating operation, and the optional filter is disclosed, but no details are given about matching behavior, ordering, or whether all sections are always returned. The output schema likely covers return structure, but edge-case behavior remains undocumented.

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 a single, front-loaded sentence with no filler. It names the resource, the action, and the parameter behavior efficiently.

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 list tool with one optional parameter and an output schema, the description covers the essential call semantics. It could be slightly richer by noting substring matching behavior, but nothing critical is missing for a competent agent.

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?

The schema only shows 'contains' as an optional string/null with no description. The tool description adds meaningful semantics by explaining it as an optional substring filter, which is exactly the missing context. More detail such as case sensitivity would be nice, but for a single optional parameter this is adequate.

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 ('List') and resource ('Prothom Alo section slugs'), and clearly mentions the optional substring filter. This distinguishes it from the sibling news-retrieval tools, which operate on articles and search queries rather than section metadata.

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 intended use is clear: call this when you need section slugs, optionally narrowed by a substring. However, the description does not explicitly mention when not to use it or name the sibling alternatives, so the usage guidance is implied rather than explicit.

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