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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds substantive value beyond that by disclosing the full response shape (stake size, ownership structure type, sources with headline and date, locations by state) and by noting brand-name inputs work. It does not say what happens when the group is unknown or ambiguous, which keeps it from a 5.

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 verb and resource, then a single dense enumeration of returned fields followed by illustrative queries. Every clause carries information, though the field list is long enough that it reads more as an inventory than a structured summary.

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?

With no output schema, the description must carry the return-value burden, and it does so thoroughly by naming each returned attribute. Combined with the example queries, an agent has enough to call it correctly; the only gap is the lack of guidance on supplying id versus name given that no parameter is required.

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 description coverage is 100%, with each of id, name, and industry already documented including the enum values, so the baseline is 3. The description adds only the parenthetical "(brand names work)", which slightly extends what the name parameter accepts but does not explain the id-vs-name selection or that at least one identifier is required despite zero required parameters.

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 opens with a specific verb and resource ("Get an owner group's ownership details") and then enumerates exactly what that entails: backers, PE stake, holding structure, parent/brands, sources, locations. An agent can tell this is an ownership/provenance lookup rather than a generic business lookup, but it never names or contrasts with the sibling tools find_businesses or lookup_business, so it falls 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?

Usage context is concrete: the description gives example questions ("who owns Heartland Dental?", "is Aspen Dental private equity?") and notes that brand names work, which tells an agent exactly what class of query routes here. It offers no explicit exclusions or guidance on when to prefer lookup_business/find_businesses instead, so it is clear context without alternatives.

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