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

Annotation readOnlyHint is true and the description uses 'Get', consistent with a read-only operation. The description adds the response fields and the source of the slug parameter, but doesn't disclose additional behavioral traits like authentication or rate limits. With the annotation covering safety, this is acceptable.

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 lines: the first states the purpose and fields, the second defines the parameter. No redundant information.

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 a single parameter, a readOnly annotation, and an output schema present, the description provides sufficient information to invoke the tool correctly. It explains where the slug comes from and what the response contains.

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 schema property has no description (0% coverage). The description compensates by defining 'slug' as a regulator slug from list_regulators results, giving the agent exact guidance on how to populate 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 clearly states the tool retrieves a full regulator profile and enumerates the contained fields (jurisdiction, authority_for, statutory_authority, hosts). This distinguishes it from list_regulators which presumably returns summaries.

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 indicates the slug should come from list_regulators results, implying a workflow of listing first then getting details. It offers clear context but doesn't explicitly name alternatives or when-not-to-use.

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