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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description's only addition is 'Returns paginated results', which restates what the per/page params already imply; it does not explain ordering, truncation, or what the paginated envelope looks like.

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 with no filler, and the resource scope is front-loaded ahead of the return note. It is efficient, though the brevity edges into under-specification for a tool spanning 13 entity types rather than being genuinely economical.

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?

This is a broad, complex query tool with a nested filters object, 13 entity variants, and no output schema. The description never explains how filters combine, what the response envelope contains, or how it relates to sibling query/search tools, so it is not complete enough for an agent to call it confidently in ambiguous cases.

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%, including a detailed per-entity breakdown of valid filters and the enum list, so the schema carries the parameter burden completely. The description adds nothing beyond 'paginated results', which does not compensate for or enrich any parameter meaning – baseline 3 applies.

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?

States a verb (query) and resource (Nitrosend entity) plus the return shape ('paginated results'), so the basic action is clear. But 'any entity' is so broad across 13 enum values that an agent cannot tell from the description how this differs from nitro_search_contacts or nitro_get_insights; that differentiation only appears buried in the entity parameter's schema text.

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 itself gives no when-to-use guidance, no prerequisites, and no named alternatives. The only routing hint ('Contact full text: nitro_search_contacts') lives in the schema's entity description, not the tool description, so the guidance is present but not where an agent reading the definition would naturally find it.

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