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

Annotations already cover readOnly, idempotent, openWorld and non-destructive, yet the description still adds real substance: unknown is 'never a negative', review signals are 'never proof', every claim is traceable to sources with timestamps, and recheck:true performs live GitHub existence checks. That goes meaningfully beyond the structured hints, though output volume/size and latency are not addressed.

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?

Purpose is front-loaded correctly, but the body is a single sprawling sentence with heavy parenthetical asides that is hard to parse. Every listed field arguably earns its place given there is no output schema, but the structure should be broken into scannable clauses.

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?

With no output schema, the description carries the full burden of describing the return value, and it does so thoroughly — requirements, unknowns, cross-role signals, projects, questions with source links, skill confidence bands, review signals, freshness and sources. An agent has enough to decide and 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 100%, so role_id, username, format and recheck are all documented already; the description mostly restates them. It adds only marginal nuance ('format markdown returns text to paste'), which justifies the baseline 3 rather than higher.

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 artifact (role-specific interview brief on one person in a role) and enumerates its contents, so an agent knows exactly what comes back. It implicitly distinguishes itself from analysis siblings by stating it is 'built from what AyHire already saved (free, no new analysis)', but it never names analyze_github_user or enrich_person, so sibling routing is left to inference.

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 'free, no new analysis' implies this is the cheap path versus the analysis/enrich tools, and 'The same person in two roles gets two briefs from the same facts' hints at call pattern. However there is no explicit when-to-use/when-not-to-use statement or named alternative, so usage is only implied.

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