get_entity

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

Without annotations, description carries full burden; it mentions returning a dict with entity info and related facts, but does not disclose potential performance implications, mutation guarantees, or other behavioral traits.

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 with three clear sentences covering purpose, arguments, and return value. 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?

For a simple retrieval tool, covers purpose, parameters, and return type. Missing details about pagination or fact count limits, but adequate for small-scale queries.

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?

Adds meaning beyond schema by noting name is case-insensitive and entity_type is optional, compensating for 0% schema description coverage. However, could provide more detail on expected values or constraints.

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?

Clearly states the tool gets all facts involving an entity as subject or object. Differentiates from siblings like search_facts by specifying the entity-centric nature.

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 alternatives such as search_facts or get_neighbors. Does not provide any when-not-to-use or context for selection.

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