entities_list_entity_registry

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

With no annotations, the description only mentions that it includes disabled/hidden entities, a minimal behavioral trait. No disclosure of read-only nature, rate limits, or other behaviors.

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?

Extremely concise (one sentence) but omits crucial parameter details. Front-loads the purpose but lacks completeness for a tool with siblings.

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?

Given the existence of multiple entity-listing siblings and an output schema, the description does not explain return value shape or filtering capabilities, leaving significant gaps.

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?

The single parameter 'domain' has 0% schema description coverage, and the tool description does not mention it at all, failing to add any meaning or usage guidance.

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 it gets a raw entity registry including disabled and hidden entities, differentiating it from other entity listing siblings that likely filter active entities. However, it could be more explicit about what 'raw' means.

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?

No guidance on when to use this tool versus sibling tools like entities_list_entities or entities_list_exposed_entities. No context about prerequisites or scenarios.

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