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

Annotations already declare readOnlyHint=true and openWorldHint=true, but the description adds meaningful behavioral context: it synthesizes from live public web sources, includes dated buying signals and stated unknowns, and guarantees source URLs for every claim. This goes beyond what the annotations alone convey, though it does not discuss edge cases like source unavailability or citation failure.

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 with no filler: the first sentence delivers the core purpose and output components, and the second enumerates focus areas. Information is front-loaded and every clause earns its place.

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 rich input schema, output schema, and annotations, the description covers the essential behavioral contract: what it synthesizes, which focus areas are supported, the cited nature of the output, and key constraints like leadership roles only. Nothing critical is missing for an agent to invoke it 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%, so the schema already documents domain and focus_areas including the default and the 'leadership' specifics. The description reinforces the focus-area list and 'roles only' constraint, adding marginal interpretive value but not significantly surpassing the 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 names a specific verb and resource: synthesize an executive one-pager on a company from live public web sources. It enumerates the output components (snapshot, findings per focus area, dated buying signals, deal risks, stated unknowns) and states every claim carries a source URL, making the tool's function concrete and distinguishable from sibling research tools.

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: call this when a cited executive one-pager on a company is needed, with focus areas controlling depth. However, it does not explicitly state when to prefer this over siblings like get_deep_research or get_market_landscape, nor does it list any exclusions or alternative conditions.

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