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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does disclose an important behavioral stance: absence of public evidence is never interpreted as proof of refusal. This is meaningful. Yet it says nothing about return values, side effects, permissions, or how evidence is weighed, leaving the behavioral picture incomplete.

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 with no filler, and the core purpose is front-loaded. The wording is somewhat abstract, which reduces immediate clarity, but the structure is tight and every clause adds meaning.

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?

For a 3-parameter tool with no output schema and no annotations, the description leaves notable gaps: explicit parameter semantics, return shape, and relationship to sibling tools like get_realizations or get_service are all missing. The single interpretive caveat is useful, but not enough to make the tool fully callable by an agent.

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 0%, so the description must compensate by explaining the parameters. It loosely references 'service/location offer' and 'locality,' which hints at the service and location parameters, but it never names them directly and does not mention realization_limit at all. An agent cannot confidently map the abstract wording to the actual input fields.

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 task: distinguishing a documented service/location offer from merely having or not having a published realization. This communicates that the tool verifies public evidence rather than just listing or fetching content. It does not explicitly differentiate from siblings like get_realizations or get_service, so it stops short of 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 implies when to use the tool: when an agent needs to determine whether public evidence documents an actual service offer at a location. It also adds an interpretive caution about absence of evidence. However, it gives no explicit when-not-to-use guidance or alternatives among the eleven sibling tools.

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