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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds value beyond that by disclosing the content of the settings payload and the operational constraint that lookups only occur for confirmed HelpWell form signups, which is not derivable from the 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?

Two sentences, front-loaded with the enumeration of returned settings and closed with the scoping constraint. The list is long but each item corresponds to a real part of the settings object, so it earns its place; only slight trimming would improve it.

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?

No output schema exists, so the description must carry the return-value burden, and it does so by enumerating the settings components. Combined with annotations covering safety and the absence of parameters, an agent has enough to call this correctly; only the lack of usage routing keeps it from being fully complete.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly avoids inventing inputs.

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 states a specific resource (LeadFuze enrichment settings) and enumerates exactly what is returned: on/off state, monthly lookup cap and usage, saved fields, ICP score rules, and per-form double opt-in and enrichment switches. That is far more than a restatement of the name. It stops short of naming a sibling, but the read-vs-write split against update_enrichment_settings is unambiguous from the names.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative tool is named. The closing sentence about lookups applying only to confirmed HelpWell form signups is a behavioral constraint, not a routing rule, so an agent still has to infer that this is the settings-read counterpart to update_enrichment_settings.

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