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

With no annotations, the description carries the full burden and does disclose important traits: the result is a sanitized public projection, owner PII is gated, and the call is a real HTTP request against the canonical endpoint. It does not state auth requirements, rate limits, or error behavior, which is a gap but not severe for a read lookup.

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?

Three short sentences, front-loaded with purpose and scope, then the return fields, then the PII routing note. Every sentence earns its place and there is no filler.

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 single-parameter read tool with no output schema, the description compensates by listing the concrete fields returned and clarifying the live-call behavior. Missing are error cases and whether authentication is required for the public view, so it is close but not fully complete.

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 already documents the single 'id' parameter as a cuid or googlePlaceId. The description adds no syntax, format, or lookup-precedence detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb+resource ('Resolve a business profile by id') and immediately scopes it as the public view. It also names the distinct PII path (pabandi:verify_owner), which separates it from sibling tools such as pabandi_discover or pabandi_search_services.

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?

Clearly signals when to use this tool (lookup by id for the public profile) and when to use an alternative (full PII via pabandi:verify_owner). It does not address when to prefer this over the discovery/search siblings, so it falls short of explicit exclusions.

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