object_query

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

No annotations are provided, so the description bears full responsibility. The term 'bounded' hints at limit enforcement, but the description omits details about pagination, cursor, max_scan limits, read-only behavior, or return semantics. It adds little beyond parameter hints.

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?

Two short sentences lead with the core purpose and then provide parameter setup guidance. 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?

Given the complex input schema with recursive Where clauses and many optional parameters, plus no annotations, the description is far too sparse. It doesn't explain the query semantics, pagination, or role of context_id. Even with an output schema, the tool is under-described.

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?

With 0% schema description coverage, the description names only model, scope, npi_types, semantic_classes, and wave_id, and omits the crucial 'where' filter, limit, cursor, max_scan, allow_global, and the nested request/context_id structure. The schema itself is highly detailed but description doesn't explain how to construct a query.

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 'Run a bounded declarative object query,' specifying the verb and resource clearly. It distinguishes from siblings by describing a declarative, bounded query rather than a direct get/traverse, though it doesn't explicitly name alternatives.

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?

It provides conditional guidance: 'waveform queries also require wave_id' and suggests which fields to set. However, it doesn't explain when to choose this tool over object_get/object_traverse or provide alternative tool names, leaving usage largely implied.

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