QueryEntity

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

No annotations are provided, so the description carries the full behavioral disclosure burden. The verb 'Retrieve' implies a read operation but no other behavioral traits are disclosed, such as scope, response format, or limitations. The three-word description adds no context beyond what the tool name already implies.

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 concise at three words and contains no fluff. However, it essentially restates the tool name and does not add enough substance to be considered efficiently informative, so it borders on under-specification.

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 large set of sibling tools with overlapping names, a three-word description is insufficient for confident selection. There is no output schema to compensate, and the description does not clarify what 'Entity Details' includes or how it differs from 'Full' variants like QueryEntityFull. The agent cannot tell when this tool is the right choice.

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 tool has zero parameters and schema description coverage is 100%, so there is nothing the description needs to explain about parameters. The 0-parameter baseline of 4 applies here.

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 states a clear action ('Retrieve') and resource ('Entity Details'), so the basic purpose is understandable. However, it does not distinguish itself from siblings like SearchEntity or QueryEntityFull, which likely also retrieve entity information. This prevents full differentiation.

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 provides no guidance on when to use this tool versus alternatives. It does not mention any conditions, exclusions, or relationships to sibling tools such as SearchEntity or QueryEntityFull. The agent must guess usage from the tool name alone.

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