orion_query_entities

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

The description details query behavior including filters (type, ID pattern, simple query language), attribute selection, pagination with defaults (limit 20, max 1000, offset 0). This goes well beyond the readOnlyHint annotation, fully informing the agent of operational 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?

The description is well-structured with an 'Args:' list, but the bullet points could be more concise. However, each sentence adds value and the format is clear and scannable.

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 6 parameters, none required, and an output schema present, the description covers all needed details: filters, pagination, defaults, and parameter constraints. No essential information is missing.

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?

Despite 0% schema description coverage, the description explains all 6 parameters with examples and defaults (e.g., 'Camera:TIMONE.*', 'status==online'), adding significant meaning beyond the input schema. Each parameter's role and usage are clearly defined.

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 'Query entities from the Context Broker', using a specific verb and resource. It distinguishes itself from sibling tools like orion_create_entity and orion_get_entity by focusing on querying multiple entities with filters.

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 explains parameters and filtering options but does not explicitly state when to use this tool versus alternatives like orion_get_entity for a single entity. Usage context is implied but not formally clarified.

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