Find Warm Paths

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

With no annotations, the description carries the burden. It discloses the scoring factors and transparency of results, which is useful context beyond the schema. However, it does not mention data sources, recency semantics, or any required setup/preconditions (e.g., must import connections first). Moderate transparency.

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 compact sentences. The first states the core function, the second elaborates on scoring transparency. Efficient, no fluff, and front-loaded with the main verb. Could arguably be one sentence but this is still clean.

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 there is an output schema, return values don't need description. The tool is a relatively simple ranked read with 2 params, and the description covers its purpose and scoring logic. Lacks preconditions like needing stored contacts (import_connections) but that is arguably implied. Overall adequate.

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 parameter descriptions are succinct ('Maximum contacts to return' and 'Target company name'). The description does not add extra semantics beyond the schema, but none are really needed; 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?

States a specific verb ('Rank') and resource ('stored contacts') and clearly distinguishes from siblings like find_alumni and find_jobs by focusing on contact warmth into a company. The description also names the output's transparency property, further differentiating it.

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?

Implies usage when ranking contacts by warmth for a target company, but does not explicitly state when to prefer this over alternatives like find_alumni or suggest_targets. No explicit when-not-to-use guidance, but the context is clear enough.

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