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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuine behavioral context beyond that: it enumerates the returned fields and, unusually, discloses a negative — contact details are excluded — which prevents an agent from calling it expecting email/phone. No auth or rate-limit info, but with annotations present the bar is met.

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?

A single dense sentence that front-loads the return payload and ends with the one disqualifying caveat. Efficient, though the trailing 'use the profile URL' is slightly ambiguous about where that URL comes from and costs a clause.

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?

With no output schema, the description carries the burden of describing returns and does so field-by-field, plus flags the contact-detail omission. What remains thin is how the slug is obtained and whether this is a pre- or post-search step, which the schema only partially covers.

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?

Only one parameter with 100% schema coverage ('Supplier slug from a search result'), so the schema carries the semantics. The description adds nothing about slug format beyond implying the profile URL is the contact path, which is baseline-adequate but not additive.

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 ('Full profile' of a supplier) and enumerates what the profile contains: capabilities, certifications, categories, products. It implicitly contrasts with search_suppliers by emphasizing 'full profile' versus search results, but never names the sibling, so differentiation is inferred rather than stated.

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?

Usage is only implied: the schema's 'slug from a search result' hints that this follows a search, but the description gives no explicit when-to-use or when-not-to-use, and never names search_suppliers or get_part as alternatives. The one caveat ('contact details are not returned — use the profile URL') is output guidance, not invocation guidance.

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