neshan_deeplink

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

With no annotations, description carries full burden. It discloses fallback to web app and return of both platform variants, but does not cover authentication, rate limits, or error handling for invalid coordinates.

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?

Description is extremely concise at three sentences, with the most important information (purpose and fallback) front-loaded. Every sentence adds value.

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 8 parameters and complexity, description adequately covers core functionality and return variants, but lacks details on coordinate constraints, parameter relationships, and output schema. An output schema exists but is not described.

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 only 25%. Description adds minimal meaning beyond schema (e.g., mention of point and routing), but does not elaborate on coordinate parameters, origin/dest, or return format, which are needed given low schema coverage.

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?

Description clearly states the tool generates deeplinks for showing a point or navigation, with specific verb 'generate' and resource 'deeplinks', distinguishing it from sibling tools that handle other mapping functions.

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?

Description mentions fallback behavior and return variants, but lacks explicit guidance on when to use this tool versus alternatives, and does not specify when not to use it.

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