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 agent knows it is a safe read operation. The description adds valuable context beyond these hints by specifying that no access code or personal info is needed and enumerating what it does NOT access (property, production, valuation, private records). This helps the agent set expectations about the tool's limitations and side effects. No contradiction with 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 sentences, front-loaded with the main action and resource. It packs the essential scope (public contact details, website links) and the key exclusions into a compact form. Every sentence adds value, and there is no redundancy or filler. It is appropriately sized for a zero-parameter read-only tool.

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?

Given the tool's simplicity (no parameters, no output schema), the description is fully complete. It tells the agent what the tool returns (company info, contact details, website links) and what it does not return or do. The sibling tools are about inquiries, so the context is clear. An agent has all necessary information to decide when to call this tool and what to expect from the result.

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 schema coverage is trivially 100%. Per calibration, a baseline of 4 is appropriate for zero parameters. The description does not need to elaborate on parameters since there are none, and it adds no parameter-specific semantics that are missing.

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 ('Read'), a specific resource ('Buckhead Energy company information'), and clarifies the scope (public contact details, website links). It explicitly lists what it does not do, distinguishing it from the sibling tools which are all inquiry-related (prepare_inquiry, request_inquiry_access, submit_inquiry). An agent can immediately understand the tool's purpose and differentiate it from siblings.

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 usage context by stating that no access code or personal information is needed, which suggests it is for public information retrieval. It also lists exclusions (does not send a message or access property/production/valuation/private records), which hints at what it is not for. However, it does not explicitly say 'use this when you need public company info' or name the alternatives. The sibling tools are clearly about inquiries, so the distinction is evident, but explicit when-to-use guidance is absent.

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