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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds valuable non-schema context by disclosing this is a 'Premium API' with a specific cost ('$0.25 USDC via x402'), which is an important constraint for an agent deciding to invoke it. It also describes the kind of data returned, adding transparency beyond the annotations.

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 two short, front-loaded sentences. The first sentence states the core purpose, and the second covers the premium/cost information. Every word earns its place; there is no redundant filler or abstraction.

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 with no output schema, the description is largely sufficient. It explains what data is returned (leadership, roles, background), notes the cost, and the schema fully documents the parameter. Missing are only minor details like response format or error behavior, which are not critical for invoking the tool correctly.

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%: the 'lookup' parameter already has a clear description and example ('Company name and job title (e.g. 'Coinbase CEO')'). The tool description does not add new meaning to the parameter; it only restates the general purpose. Per rubric, when schema coverage is high, a baseline of 3 is appropriate.

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 'Retrieve' with a clear resource: 'executive profile information for a company.' It enumerates what is included ('leadership details, roles, and professional background'), which distinguishes it from sibling tools like business_info or company_verification. The tool name and description align perfectly, leaving no ambiguity.

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—whenever an executive profile is needed—but gives no explicit guidance about alternatives or when not to use it. There is no mention of sibling tools or exclusion criteria, and the 'for a company' phrasing only loosely frames the use case. The agent must infer usage from the purpose alone.

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