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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the description is not obligated to restate it. What it adds is a content inventory (company info, services, articles, contact), which helps set expectations about the payload. It says nothing about whether results are keyword-matched, exhaustive, or how a broad topic behaves, and with an output schema present it is reasonable it omits return structure.

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?

Two sentences, front-loaded with the content the tool returns, followed by the usage instruction. No filler or hedging. The first sentence is a loose list but each item earns its place by signaling an available content category.

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?

The tool is simple (one optional parameter, read-only, output schema present), and the description covers purpose and content adequately. The gap is that 'topic' is optional and the description never says what happens with no topic — full profile dump, error, or default match. Given siblings that also surface intel, a word on scope would have made it complete.

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 coverage is 100% and the schema already labels the single optional 'topic' parameter as 'What the user needs help with'. The description nevertheless adds value by giving two example topics ('CTV monetisation in APAC', 'SSP selection') that convey the expected phrasing and granularity. That goes slightly beyond the baseline for a fully documented single parameter.

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 set: DigiAdapt's identity, its advisory services, founder articles and contact details. That is concrete enough to tell an agent this is a company/service-profile lookup rather than a market-data query. It stops short of differentiating itself from siblings like get_adtech_intel or search_intel, which the agent must infer.

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 second sentence gives an implied usage pattern: pass a topic and get matching services, with two illustrative topic examples. There is no statement of when NOT to use it, nor any routing to the sibling intel/search tools, so selection between them is left to inference.

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