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

With no annotations, the description carries the behavioral disclosure burden. It does reveal that the tool checks ~30 tools and returns existence plus extracted entities, but it does not mention latency, rate limits, auth requirements, or failure behavior. For a read-only sweep, this is a moderate but acceptable gap.

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 a single sentence with no filler. It front-loads the person-focused scope and then efficiently covers the tool count, input, and output, making every clause informative.

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 output schema exists and there is only one required parameter, the description covers the essential purpose, input, and output. It omits operational caveats such as runtime or result volume, but nothing critical is missing for an agent to make a first call 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 0%, so the description is the only source of parameter meaning. It adds value by clarifying that the 'name' parameter accepts one name or handle. It does not give format examples or state whether emails are valid, but it provides enough semantic guidance for a single required string 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 clearly states the action ('checks ~30 username/email/social presence tools'), the input ('one name/handle'), and the output ('where it exists plus extracted entities'). It conveys a specific person-focused scope, but it does not explicitly differentiate from sibling tools like correlate_sweep, username, or social.

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 phrase 'Person-focused sweep' implies when this tool should be used, and 'for one name/handle' gives context. However, there are no explicit when-not-to-use conditions or references to alternative tools, so an agent must infer how it compares to similar sibling tools.

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