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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds useful behavioral context: cards are cross-site marketing assets assembled from brandscripts and proofs, and filters restrict results to one product or lifecycle. No contradiction with 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 compact and readable, but the opening sentence largely repeats the tool title verbatim, and the next sentence partially overlaps with it. It is not bloated, but there is minor redundancy.

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 and read-only annotations, the description covers the key usage context: what the registry contains, its provenance, and available filters. It does not explicitly explain how personas are returned, but the output schema handles return structure.

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 description coverage is 100%, so the baseline is 3. The description restates the filter semantics and adds that product filters to one product, but it does not materially enrich beyond the schema's parameter descriptions.

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 names a specific resource, the Pitboss marketing-asset registry, and clarifies its contents as typed cards plus personas built from brandscripts and proofs. It is clear about the resource, though it does not explicitly differentiate itself from sibling get_brandscripts or get_insight_cards.

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 conveys the domain and optional filters (?product, ?status), giving some sense of when to call it. However, it does not state when to prefer this tool over sibling get_* tools or provide explicit exclusion/alternative guidance.

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