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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered; the description adds useful context that it is free with no account and that results include agent-facing contact/booking capability flags. It does not disclose failure behavior — neither parameter is required, yet the description never says what happens when both slug and domain are omitted, nor what occurs on a miss (error vs empty result).

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?

Front-loaded with the identity of the resource and the two lookup keys, with the usage exclusion placed near the end where it doesn't block the core read. The single dense sentence with a long comma-chained list of return fields is heavy, but every clause carries information.

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?

An output schema exists, so the enumeration of return values is partly redundant, though it usefully signals that prices and open-now status are confirmed rather than scraped. The real gap is the missing rule for zero-argument calls and for providing both keys, which matters given 0 required parameters.

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 100% and both parameters already carry examples, so the description's gloss ("the name before .inite.ai") largely duplicates the schema. It adds no precedence rule for supplying both slug and domain, which is the one genuinely ambiguous case the schema leaves open.

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?

Names a specific resource (one business) and the two keying mechanisms (INITE slug or domain), then enumerates the payload: services with prices, hours/open-now, locations, company facts server. That is far more than a restatement of the name. It falls short of 5 because it never contrasts itself with the sibling find_business, leaving the single-vs-search distinction to be inferred from the title.

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?

Provides an explicit exclusion clause: for choosing an AI tool or app, use match_tools or atlas_lookup on the INITE Atlas, not this. It also states cost/prerequisite conditions ("Free, no account"). However, it gives no guidance on when to call this versus find_business or inite_connect, so the sibling routing is only half-covered.

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