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 fully covered without the description. The description adds genuine context by disclosing the subject matter the response will cover (matching mechanics, cost), but says nothing about response format, length, or that no arguments are accepted.

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 compact sentence with the subject (TBG) front-loaded and the secondary details trailing in a parenthetical. Every clause adds distinct content — identity, offerings, area, matching, cost — so nothing is padding, though the sentence-fragment construction is slightly harder to parse than a plain verb phrase would be.

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, read-only informational tool with annotations covering safety and no output schema to explain, the description covers what an agent needs to decide to call it and what it will get back. Only a light when-to-use cue and any note about the absence of arguments are missing.

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 takes zero parameters, which is the baseline-4 case; there is nothing for the description to disambiguate. The description correctly reflects the argument-free nature of the call, and no parameter clarification is needed or 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 names the specific resource (TBG / The Brett Group) and enumerates the content returned: identity, offerings for three audience types, geographic service area, matching mechanics, and cost. That is far more specific than a tautology and lets an agent distinguish it from contact_tbg or check_service_area. It lacks an explicit verb ('returns'/'describes'), but the scope is unambiguous.

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?

Usage is only implied: an agent can infer this is the orientation/'about us' tool to call when a user needs company background or pricing context. There is no explicit when-to-use statement, no statement of when NOT to use it, and no routing to specific siblings such as list_project_options or apply_to_network when the user actually wants to act.

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