Resolve a Paziresh24 URL

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, covering the safety profile. The description adds a small amount of context (the classification outcome and the chained next tool) but nothing beyond what the output schema and annotations already establish.

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?

Two short sentences, front-loaded with the transformation and followed by the trigger plus next-tool routing. No filler or repetition.

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?

An output schema exists and annotations cover safety, so return values and side effects need no further explanation here. The only small gap is behavior on an unrecognized or malformed link, which is not stated anywhere.

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 is one parameter at 100% schema description coverage, and the schema already spells out the accepted path forms (/dr/, /center/, /factor/v2/) and encoding tolerance. The description only restates that the input is a paziresh24.com link, so baseline 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?

States a specific verb+resource (turn a paziresh24.com link into kind + slug + clean URL) with an explicit output shape, so the agent knows exactly what comes back. It is clearly distinguishable from the sibling lookup tools (pz_doctor, pz_center) which it feeds into.

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?

"Use when the user pastes a link" gives the trigger condition, and the second sentence names the two follow-up alternatives (pz_doctor for a doctor, pz_center for a hospital/clinic) with the condition that selects each. Routing guidance is explicit rather than inferred.

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