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

With no annotations, the description carries the full disclosure burden. It does earn credit for naming a conditional behavior — the cadence heads-up appears only when the relationship is in a Watch state — but omits what happens when the contact is unknown or ambiguous (string accepts id or name), and whether the brief is cached or computed live.

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 with the content enumeration front-loaded and no repetition. 'The Brief Me hero tool' is the one expendable clause — it consumes the highest-attention position without telling the agent anything about behavior.

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 one-parameter read tool with no output schema, the description covers the essential unknown: what comes back, including the conditional Watch-state section. The remaining gap is failure/ambiguity handling for the contact identifier, which is a real but secondary omission.

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 single parameter documents its own format with an example. The description adds only that the contact is a 'demo contact', which is marginal beyond the schema; baseline 3 applies when the schema does the heavy lifting.

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 and resource — returns a synthesized pre-interaction brief for a demo contact — and enumerates what it contains (personality read, opener, things to avoid, cadence heads-up). The 'hero tool' framing is marketing noise rather than scope, and it doesn't explicitly distinguish itself from the sibling get_contact_profile.

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 'pre-interaction brief' implies timing (use before engaging a demo contact), but there is no explicit when-to-use, no when-not, and no routing to or from the plausible alternatives (get_contact_profile, get_radar, demo_temperature_check). Usage is inferable rather than stated.

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