Create task deep-link

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

Annotations (readOnlyHint=true, idempotentHint=true, destructiveHint=false) are fully supported: the description states 'makes no network call and creates no task' and 'pure formatter'. It adds context that the URL follows a specific format, which is useful beyond the annotations.

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?

Four sentences, each essential: tool purpose, URL format, no-side-effect assertion, and usage guidance. Front-loaded and efficient with no redundancy.

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?

Even without an output schema, the description fully explains the return format and the broader workflow (user completes booking on-platform). It clarifies the limitation of agent-side task creation, making the tool's role in the flow complete.

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%, maintaining a baseline of 3. The description adds value by specifying the source of each slug (e.g., professional_slug from search or get, service_slug from list), providing execution context not in the schema.

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 it builds a deep-link URL for the Muovi task creation flow, pre-filled with a professional and service. It distinguishes this from sibling tools by explicitly labeling it as a 'pure formatter' that makes no network calls or task creation.

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 says the tool should be used after selecting a professional and service, and the URL should be surfaced to the user for completing the booking on Muovi. It also warns that the agent cannot create tasks server-side, guiding appropriate use.

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