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

No annotations are provided, so the description carries the full burden. It clearly signals a read operation via 'List' and 'Retrieve' and discloses pagination support. However, it does not mention authentication requirements, error behavior, or result format, leaving only partial transparency.

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 three sentences: the first states the core action, the second adds example content types, and the third notes pagination. Each sentence contributes useful context with no wasted words, though it could be slightly tighter.

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 and no annotations, the description could do more to explain the return structure or error/success outcomes. It covers the core operation and pagination hint, but it lacks explicit usage distinction from the key-specific sibling and does not explain what happens when no data exists or the entity is not found.

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's phrase 'Supports pagination' reiterates the page/pageSize parameters already documented in the schema, and it adds no additional parameter-level meaning beyond what the schema provides.

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 opens with 'List all custom data key-value pairs associated with an entity,' using a specific verb and resource. It clarifies entity types ('services, resources, or domains') and 'all' implicitly distinguishes from sibling getCustomDataForEntityByKey. However, it does not explicitly name the alternative tool, so it misses the top tier.

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 implies when to use the tool (when you need all custom data for an entity) and mentions pagination for large datasets, but it never explicitly contrasts with getCustomDataForEntityByKey or other sibling tools. No when-not-to-use guidance or alternative tool names are provided.

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