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

Beyond the readOnlyHint and openWorldHint annotations, the description adds critical behavioral details: it lists the returned fields, explicitly states that phone/email/whatsapp are never returned, and defines the profile_url as the only contact channel. This informs the agent of data limitations and usage constraints.

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 efficient and well-structured: it opens with a clear purpose sentence, then lists return fields, followed by a behavioral note and a usage tip. No redundant words, and critical info appears early.

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?

Despite lacking an output schema, the description comprehensively enumerates all expected return fields and explains how to use the profile_url for task creation, referencing a sibling tool. It covers the main use case end-to-end, making it self-contained for an agent.

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?

The single parameter 'slug' is well-described in the schema with an example and sourcing advice. The tool description repeats this sourcing advice (obtain from muovi_search_professionals) but adds minimal new semantic meaning beyond the schema, which already provides 100% 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?

The description clearly states the tool 'Fetch the full public profile for a single Muovi-verified professional by slug,' specifying the action, resource, and input. It lists the returned data fields, distinguishing it from sibling tools like muovi_search_professionals (which returns lists) and muovi_get_reviews.

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 advises obtaining the slug from muovi_search_professionals and contrasts with muovi_create_task_link for deep-linking, providing clear when-to-use guidance. However, it does not explicitly state when not to use this tool (e.g., for reviews or lists), though the purpose implicitly covers that.

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