İstanbul anlık trafik yoğunluk indeksi

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the agent knows this is a safe, read-only operation. The description adds useful behavioral context: the value is live and fetched fresh on every call, and it is a 0–100 index. This goes beyond the annotations without contradicting them.

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 compact and front-loaded: it states the subject, source, scale, and freshness in two short sentences. Every sentence adds value, and the bilingual phrasing is not redundant because it reinforces the meaning for different language models.

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 tool has no parameters and an output schema exists, so the description does not need to explain return values. It covers the key facts: what is measured, the scale, the source, and the live nature. A minor gap is that it does not state whether the value is a percentage or a raw index, but the 0–100 scale is sufficient for most use cases.

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?

There are zero parameters, so the schema provides no parameter documentation. The description compensates by explaining what the returned value represents (0–100 index, citywide, live), which is the only semantic information an agent needs. A baseline of 4 is appropriate for a parameterless tool.

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 clearly states the tool returns Istanbul's live citywide traffic density index from the metropolitan transport centre, using a 0–100 scale. It distinguishes itself from sibling tools by naming the specific data source and metric, so an agent can tell it apart from other data-fetching tools.

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 description implies this is a simple, no-parameter, live-data retrieval tool and notes it is refreshed on each call. It does not explicitly name alternatives or exclusions, but given the zero-parameter schema and unique subject matter, the usage context is clear enough.

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