find_entities

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

With no annotations provided, the description carries full burden. It discloses two behavioral modes (Grail DQL vs classic API) and the required type() clause. However, it does not mention authorization needs, rate limits, or that the operation is read-only, leaving gaps in transparency.

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 with two sentences, no redundant words. It front-loads the main action and provides key usage tips. Could be slightly more structured (e.g., bullet points) but overall efficient.

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 tool has 5 parameters, no output schema, and no annotations, the description is incomplete. It covers the entitySelector constraint and classic mode, but omits details on pagination (pageSize, from, to), return value format, and potential errors or limits. For a complex query tool, more depth is needed.

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 40% (2 of 5 parameters described). The description adds important context for entitySelector (must include type()) and useClassic (for Gen2 tenants), but fails to explain 'from', 'to', and 'pageSize' parameters which are left to their schema definitions. This partially compensates for low coverage but not fully.

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 that the tool queries Smartscape entities via Grail DQL, with an alternative classic mode. While it distinguishes from other entity tools by mentioning the DQL path requirement, it could be more explicit about the scope of entities queried and the returned format, which prevents a 5.

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 explicit guidance on when to use the classic API (useClassic:true for Gen2 tenants) and a necessary condition for the entitySelector (must include type() clause). However, it does not compare this tool to siblings like get_entity or list_entity_types to help decide when to use which.

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