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

Annotations provide readOnlyHint=true, and the description adds context about the response contents (firmographics, licensing, offices, counts, HATEOAS links) without contradicting annotations. It does not disclose additional behavioral traits like rate limits or authentication, but the safety profile is already covered by 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?

The description is two sentences: the first defines the tool's output, the second explains the slug parameter. It is concise, front-loaded, and every sentence adds value.

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 an output schema present, the description need not enumerate return fields, but it highlights key components and HATEOAS links. For a single-parameter read-only tool, the description provides sufficient context, including the source of the slug and the full-profile scope.

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 0% as the schema only lists 'slug' as a string with no description. The description explains slug as a URL-friendly unique provider identifier from search_providers results, adding semantic meaning about format and origin that schema lacks.

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 uses a specific verb 'Get' with a resource 'full provider profile' and lists contents (firmographics, licensing, offices, counts, HATEOAS links). This clearly distinguishes it from sibling tools like get_regulator or get_slot, which target different entities.

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 implies usage context by stating the slug comes from search_providers results, indicating a prerequisite workflow. However, it does not explicitly exclude alternatives or state when not to use it, though the specificity of 'provider profile' makes the purpose clear.

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