get_news_by_ressort

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

No annotations are provided, so the description carries the full burden. It only states the basic purpose with no disclosure of return format, pagination, error behavior, or authentication needs. The read-only nature is implied by 'Get' but not made explicit or expanded upon.

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 sentence that front-loads the core action and resource. It is concise with no redundant words, and every part directly contributes to understanding the tool's purpose.

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 output schema exists and parameters are well documented, covering return values and input details. However, the description lacks usage guidance relative to sibling tools and does not mention any behavioral constraints. For a simple get tool it is near-complete, but the missing sibling differentiation and behavioral context prevent a higher score.

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 provides 100% description coverage for both parameters, so the schema already explains 'ressort' and 'limit'. The description adds no additional meaning beyond restating 'ressort/category', which is already in the schema. Baseline 3 is appropriate.

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 the specific verb 'Get' with the resource 'news' and a clear filter 'by ressort/category'. It differentiates from sibling tools like get_latest_news (which suggests unfiltered latest news) and search_news (which suggests keyword-based search) by specifying a category filter.

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 context implies using this tool when news needs to be filtered by a category, but there is no explicit when-to-use/when-not-to-use statement or mention of alternatives. The sibling names provide some clues, but the description itself offers no direct guidance on choosing this tool over others.

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