NOVAI oracle anchors by issuer entity

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

No annotations are provided, so the description carries the burden of disclosing behavioral traits. It states it returns a list with specific fields, which is a read-only operation. However, it does not mention potential large result sets, pagination, ordering, or any limitations. The description is adequate but not transparent about these aspects.

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 two sentences, directly stating the action and the return fields. It is front-loaded and concise, with no unnecessary 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 lack of output schema and annotations, the description covers the core purpose and return fields but omits details like pagination, result limits, or ordering. It is complete enough for basic use but lacks context for more advanced or corner-case queries.

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?

All parameters have descriptions in the input schema, so baseline is 3. The description summarizes the entity and block height range but does not add significant new meaning beyond the schema definitions. It does list return fields, which helps context but not directly parameter semantics.

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 the tool lists oracle anchors by entity within a block height range, optionally filtered by timestamp. It specifies the resource and filtering criteria. However, it does not explicitly differentiate from sibling tools like novai_get_oracle_anchor or novai_get_oracle_anchors_by_tag, so it misses some distinction.

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 implies usage for listing anchors for a given entity but does not provide explicit guidance on when to use this tool versus alternatives. It lacks when-not-to-use advice and does not reference sibling tools for comparison.

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