donanimhaber_sections

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

No annotations are supplied, so the description carries the full burden, and it discloses only one behavioral trait: the data is "parsed from the homepage," implying a live scrape that may be incomplete or change with the page layout. It says nothing about whether the result is cached, how many sections are typical, whether the call is read-only or has side effects, or any rate/availability constraints for a scraping-backed endpoint.

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 with no filler: it identifies the resource, the domain, the returned fields, and the data source in one pass. Nothing in it is redundant or padded.

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?

With zero parameters and an output schema present, the description does not need to enumerate return values, and it is complete for calling the tool correctly. The remaining gap is operational: as a homepage-scraping endpoint with no annotations, a hint about reliability or when to fall back to another tool would round it out.

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 tool takes zero parameters, so there is no parameter meaning to add; the baseline for a parameterless tool is 4. The description correctly does not invent inputs and instead spends its words on the return shape.

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 names a specific resource (all news sections/topics on donanimhaber.com) and the exact fields returned (name + slug + URL), so an agent knows precisely what it gets. It stops short of explicitly distinguishing itself from the sibling donanimhaber_section, leaving the agent to infer that this is the discovery/index call versus the per-section news call.

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?

Usage is only implied: the phrase "all news sections/topics" suggests using this to discover available sections, but there is no explicit statement of when to call it instead of donanimhaber_section or donanimhaber_latest. No prerequisites, exclusions, or alternative routing is given.

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