Freelance Client Management Guide — 7 Steps to Never Lose a Client

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, fully covering the safety profile of this static content-delivery tool. The description adds value by detailing the content scope (what topical ground the guide covers), which serves as behavioral context beyond the annotations. No contradiction with annotations; description just doesn't deepen the behavioral profile much beyond content enumeration.

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 purpose sentence is front-loaded and information-dense, which is good. However, the trigger-phrase list is excessive — 11 full query examples spanning two languages consume roughly half the description. While routing hints are useful, this level of enumeration dilutes conciseness and could have been trimmed to a few representative examples.

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?

This is a low-complexity tool: 2 optional parameters both fully documented in the schema, annotations carrying the full safety profile, and no output schema needed. The description thoroughly explains what content the guide provides (7 steps, topics covered), so an agent has everything necessary to invoke it correctly. Nothing essential is missing for the tool's simple nature.

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 100%, with both parameters (lang and response_format) fully described including enums and defaults. The description adds nothing about parameters or their values, but with complete schema coverage the baseline of 3 is correct — the schema does the heavy lifting and the description need not repeat it.

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 states a specific verb and resource: 'Get a complete 7-step guide for managing clients as a freelancer,' and enumerates the exact topics covered (lead qualification, follow-ups, interaction history, pipeline analysis, loyalty). It clearly differentiates from siblings such as noto_freelance_prospection_guide and noto_freelance_productivity_tips by centering on client management and retention specifically. Purpose is unambiguous.

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 provides an explicit 'Use when someone asks:' section with 11 concrete trigger phrases in both French and English, giving clear routing guidance. However, it never states when NOT to use this tool or names alternative siblings (e.g., the prospection or productivity guides) for related-but-distinct intents, leaving exclusion logic to inference.

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