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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds real value by disclosing what the response contains (tool counts, rank, integration direction, categories, warehouse connections, similar CDPs, page URL) — meaningful given no output schema. No pagination/auth caveats, but this is a single-object lookup so little is missing.

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?

Front-loaded with the verb and resource, which is good, but the return-facet list becomes one very long run-on sentence that is hard to scan. Every item arguably earns its place since there's no output schema, but the structure could be broken into a scannable list.

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 compensates well by enumerating the return facets, so an agent knows what to expect. The main gap is absent guidance on when to pick this versus the comparison or stack siblings.

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?

Single parameter with 100% schema description coverage and an example set (Segment, Braze, Adobe Experience Platform), so the schema fully carries semantics. The description adds nothing beyond the schema for the 'name' argument, which is the baseline expectation here.

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?

Specific verb ('look up') and resource ('one customer data platform'), explicitly singular in contrast to the plural list_cdps sibling. It enumerates the returned facets, so the agent knows exactly what data comes back. It doesn't name alternatives like compare_cdps or get_tool, 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: fetch a single CDP's profile. There is no explicit when-to-use versus list_cdps, compare_cdps, or check_stack, and no stated prerequisites. An agent must infer the selection rule from the singular scope.

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