entities_list_entity_registry

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

Adds behavioral info about including disabled/hidden entities, but with no annotations, misses other traits like read-only nature, performance implications, or pagination.

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?

Single concise sentence with front-loaded verb, no wasted words.

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?

Adequate for a simple tool with output schema, but could add parameter explanation and more behavioral context to fully compensate for lack of annotations.

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?

Does not mention the optional domain parameter at all. With 0% schema description coverage, description should compensate but fails to explain how to filter by domain.

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?

Description clearly states 'Get raw entity registry' and explicitly includes disabled/hidden entities, distinguishing it from sibling tools like entities_list_entities.

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?

Implied usage for raw registry retrieval, but no explicit guidance on when to use this over alternatives like entities_list_entities or entities_get_entity.

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