search_by_id

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It says only 'searches by product ID', with no information about required coordinates (latitude/longitude), return format, filtering behavior, or side effects. This is a significant gap for a tool with three required parameters.

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 short sentence, which is concise. However, it is so minimal that it borders on under-specification, similar to the 'Process' example. It is not inappropriately long, but it lacks structured detail that would make it more informative.

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?

Given three required parameters, no output schema, and no annotations, the description should explain more about the expected behavior, such as why latitude/longitude are needed or what the search returns. The current description is incomplete for a tool of this complexity, leaving important context unaddressed.

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 coverage is 100%: all three parameters (productId, latitude, longitude) have descriptions in the schema (e.g., 'Kullanıcı enlem koordinatı' for latitude). The description adds no additional parameter meaning beyond the schema, so the baseline score of 3 applies.

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 'Ürün ID'si ile arama yapar' clearly states the tool searches by product ID. It uses a specific verb ('arama yapar') and resource (product ID), making its purpose clear. However, it does not explicitly distinguish itself from sibling tools like search_products, though the name and description imply a specific ID-based lookup.

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 gives no guidance on when to use this tool versus alternatives such as search_products or find_cheapest. It does not mention prerequisites, context, or when an ID-based search is preferred over other search methods.

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