View Business Profile

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

No annotations are provided, so the description must indicate the tool's behavior. Words like 'Show' and 'See' convey a non-destructive read operation, and it adds context about returning both current profile data and missing items. This is sufficient for a zero-parameter view tool, though it does not explicitly state side-effect safety.

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?

Two concise sentences each provide distinct value: the first states exactly what the tool does, and the second clarifies the output value. There is no redundant wording or 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 simple zero-parameter read tool, the description covers the key aspects: what it shows (profile and setup status) and what users gain (knowing what's missing). It does not enumerate all possible profile fields, but that is not necessary for selection or invocation with no inputs. Overall, it is complete enough for this tool's complexity.

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, and the description adds no parameter-specific details (none are needed). The baseline for zero-parameter tools is 4, and the description adequately focuses on the tool's purpose without needing to compensate for schema gaps.

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 uses a specific verb ('Show') with a clear resource ('current business profile and setup status'). It distinguishes itself from siblings like setup_business and update_profile by focusing on viewing rather than modifying.

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: to check what is known about the business and what is missing. While it does not explicitly mention alternatives or exclusions, the context of 'setup status' and 'what's still missing' clearly positions it as a discovery/read tool before performing setup or updates.

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