fetch

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

With no annotations provided, the description carries the full burden of disclosing behavior. It indicates a read-only retrieval operation by saying 'Fetch full details' and lists output content, but it does not mention error behavior, required permissions, or whether the response is complete or paginated. This is adequate for a simple lookup but not richly transparent.

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?

The description is a single sentence that front-loads the core action, resource, and key output categories. There is no filler or redundant content, and it remains highly readable despite packing in the input constraint and return scope.

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 one-parameter tool, the description covers the input source (search result) and the output facets (services, hours, timezone, booking). However, it does not address the existence of get_business, which is a likely alternative, nor does it explain when to use one over the other. Without an output schema or more detail, the description is adequate but leaves a notable gap in tool selection.

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 schema only defines 'id' as a string with no description, leaving 0% schema coverage. The description compensates by specifying that the id is a 'business id returned by search', which tells the agent both the semantic meaning of the parameter and its expected provenance. This is useful context beyond the raw schema.

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 states a specific action ('Fetch full details') and resource ('one business id'), and enumerates the returned information: services, hours, timezone, and booking. It is clear about what the tool does, but it does not differentiate from the sibling get_business, which likely overlaps in purpose.

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 phrase 'returned by search' implies the tool should be used with a business id obtained from the search tool, giving some usage context. However, no explicit exclusions or comparisons are provided against get_business, check_availability, or create_booking, so the agent must infer when this is the right choice.

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