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

The readOnlyHint and openWorldHint annotations already establish that this is a safe, non-destructive read. The description adds that each entity comes with a short summary, which is useful return-context, but it does not mention pagination behavior, ordering, or authorization requirements beyond what the schema implies.

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 a single front-loaded sentence with no wasted words. It communicates the core operation and result shape efficiently.

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?

For a simple three-parameter list tool with annotations covering safety, the description is largely complete: it states scope, the one-type filter, and that each result has a short summary. The main omission is any explanation of what the short summary contains or how results are ordered.

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 67%, with limit and entityType described but campaignId left undocumented. The description only implicitly maps 'campaign's' to campaignId and 'one type' to entityType, adding little beyond the schema while not compensating for the missing campaignId detail.

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 verb and resource: it lists a campaign's entities, scoped to one entity type. It does not explicitly distinguish itself from siblings such as search_entities or get_related_entities, but the purpose is still clear from the text alone.

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 phrase 'of one type' implies this is for enumerating entities of a single kind within a campaign. However, there is no explicit when-to-use guidance, no exclusions, and no named alternative for filtered searches or single-entity retrieval.

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