Get business profile

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

With no annotations provided, the description relies on 'Return' to signal a read-only operation, but it does not disclose additional behavioral traits such as caching, data freshness, or error handling. It provides basic transparency but leaves room for more.

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?

A single sentence efficiently lists the returned fields with no redundancy. The description is front-loaded with the purpose and enumerates contents compactly.

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 zero-parameter tool with no output schema, the description fully enumerates the return payload (name, tagline, hours, address, phone, pickup/delivery), making it complete for its complexity. There is no missing essential information.

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 input schema has zero parameters, and the description naturally does not need to explain parameter behavior. The baseline for zero-parameter tools is 4, and the description meets this without adding unnecessary detail.

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 the verb 'Return' with the specific resource 'bakery's core profile' and enumerates the fields, clearly distinguishing it from sibling tools like get_menu or check_custom_order_availability. This is a specific verb+resource with clear scope.

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 the tool is used when the bakery's general profile information is needed, which is clear context for the given zero-parameter tool. However, it does not explicitly state exclusions or alternatives to sibling tools, so it falls short of a 5.

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