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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds one genuinely new fact — availability in every package tier ('Her pakette') — but says nothing about year defaults, out-of-range handling, or whether values are current-year versus historical.

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?

Very short with no padding, and the resource name is front-loaded. However, the raw endpoint path (`GET /v1/mevzuat/asgari-ucret`) and the opaque 'Her pakette' fragment are stitched together without connective structure, leaving an under-specified rather than efficient definition.

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 one-optional-parameter read tool with no output schema and readOnly annotations, the field list partly conveys what comes back (gross, net, daily). The critical missing piece is default-year semantics and the unit/period of the returned amounts, which an agent needs to call it correctly.

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 0% for the single parameter 'yil', so the description must compensate and does not: it never mentions the year filter, its 2000–2100 bounds, or that it is optional and presumably defaults to the current year. 'Günlük' hints that daily figures are derived, but no parameter meaning is added.

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 the resource (asgari ücret) and enumerates the three figures returned (brüt, net, günlük), which an agent can distinguish from siblings like vergi_maas or ekonomi_enflasyon. It lacks an explicit verb (fetch/retrieve) and reads as a title restatement plus field list, but the field enumeration carries real identifying value.

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?

No guidance on when to pick this over vergi_maas or other economy siblings, and no statement about what happens when 'yil' is omitted. 'Her pakette' describes plan availability, not usage conditions, so the agent gets no routing or prerequisite information.

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