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

With no annotations, the description must carry behavioral disclosure. It usefully states that the tool returns an access refusal and excludes freshness, which are important traits beyond the empty schema. However, it does not explain whether refusal is unconditional, what conditions cause it, what permissions are required, or what the structured refusal contains.

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, front-loaded with the primary behavior and followed by a concise exclusion. Every sentence adds relevant information, with no filler or repetition.

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?

There is no output schema, so the description should explain the return value more fully. It identifies the output as a 'structured access refusal' but does not describe the structure, whether it is always returned, or what an agent should do with it. The crucial limitation is stated, but the definition remains incomplete for a tool whose only output is a refusal.

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, so there is no parameter semantics to clarify. The schema is empty and fully described by its coverage, making the baseline score of 4 appropriate.

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 specific verb and target: 'Returns the structured access refusal for the oracles family.' It also adds a scope exclusion ('Does not return freshness'). The purpose is clear, though the phrase 'oracles family' is not defined and the name get_oracles could suggest data retrieval rather than refusal.

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 gives no explicit guidance on when to use this tool versus alternatives. It only notes that it does not return freshness, which is a negative hint but not a use case or routing rule. No sibling tool is named as an alternative.

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