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

With no annotations, the description carries the full behavioral burden and does well on cost: it discloses that credit spend scales with targets, is bounded by max_targets, caps near ~175 credits, and that actual cost is returned in the response. It does not clarify whether the tool persists/writes anything (e.g., a stored queue) or is purely a read/compute operation, which is a remaining gap given the total absence of 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?

Four tightly packed sentences that are front-loaded with the purpose, then the pipeline, then the cost model. Every sentence carries information and none repeats the schema or title.

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 three-parameter composite tool with no output schema and no annotations, the description covers purpose, internal mechanics, and cost well. The one shortfall is that with no output schema it should be a bit more explicit about the returned structure of the 'prioritized outreach queue' beyond a single phrase.

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%, so the schema already documents all three parameters, including that each target costs ~3 credits and the default keyword list. The description adds only the aggregate framing ('bounded by max_targets', '~175 credits'), which is marginal value beyond the structured fields. Baseline 3 is appropriate.

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 verb (map) and resource (professional graph around a target company) and even outlines the internal pipeline: find decision-makers, pull posts/reactions/comments to identify engagers, score connections, produce an outreach queue. This clearly distinguishes the tool's scope. However, it never names the sibling tools it bundles (score_connections, get_outreach_queue, traverse_graph), so an agent must infer the difference itself.

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 implied by the workflow description — reach for this when you want an end-to-end prioritized outreach queue for one account. But there is no explicit when/when-not guidance, no recommendation to use this instead of the individual scoring/queue tools, and no prerequisite or exclusion stated. The agent is left to infer the selection criteria.

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