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

With no annotations, the description carries the full burden. It discloses what the payload contains (tier, references, certifications, pricing, hosting, languages), which is genuinely informative, but says nothing about read-only nature, authentication, rate limits, or not-found behavior for an unknown slug. Adequate for a read lookup but with clear gaps.

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 front-loaded sentence with no filler; the resource is named first and the field list follows. The parenthetical inventory is dense but every item conveys returned content.

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 correctly compensates by enumerating the profile's contents. It omits error behavior for invalid slugs and any usage context, but for a one-param read tool the return-value coverage is the main obligation and it is met.

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% and there is only one parameter, so the schema fully documents 'slug' as a string sourced from search_partners. The description adds no format or lookup semantics beyond that, making the baseline 3 appropriate.

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 and resource ('Full profile of one partner') and enumerates the two data sources the profile draws on, so the agent knows this is a single-entity detail fetch. It does not explicitly contrast with siblings like match_partners or search_partners, but the singular 'one partner' scope makes the distinction inferable.

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 contains no when-to-use guidance, no prerequisites, and no mention of alternatives. The only workflow hint ('Partner slug from search_partners') lives in the schema, not the description, so the description itself provides no routing help.

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