get_entity

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

Description mentions returning all incoming and outgoing relationships, which is a behavioral trait beyond a simple fetch. However, without annotations, it does not disclose potential depth limits, performance implications, or whether relationships are shallow or deep.

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 sentence, no fluff, front-loaded with purpose.

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 an output schema present, description does not need to detail return values. However, the lack of usage guidelines and parameter semantics makes the description incomplete for an agent to confidently invoke the tool.

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 coverage is 0% meaning no parameter descriptions in schema. The tool description does not explain the parameters 'name' or 'project', leaving the agent to infer meaning from their names alone.

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 the verb 'Get', the resource 'entity', and the scope 'with all its incoming and outgoing relationships'. This distinguishes it from sibling tools like 'search_knowledge' or 'get_project_graph'.

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 like 'get_project_graph' or 'search_knowledge'. No exclusions or context provided.

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