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

Annotations already declare readOnly, idempotent, and closed-world, so safety is covered; the description's added value is the content inventory, telling the agent what data surfaces without a probe call. It says nothing about staleness or how availability/contact fields are maintained, but for a zero-argument static profile read that is a minor omission.

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, zero filler: the first lists the returned fields, the second states when to reach for it. The content inventory is front-loaded ahead of the routing hint, which is the right order for a zero-param tool.

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 compensates by naming the fields the caller will receive, which is the key missing piece. Combined with annotations covering safety and a schema requiring no arguments, an agent has everything needed to call this 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?

The schema takes zero parameters and is fully self-describing, so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter guidance is needed or missing.

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 enumerates exactly what the tool returns — role, employer, location, availability, contact email, public profiles — so the agent knows the payload before calling. The clause 'about the person rather than a project' separates it from get_case_study and list_projects without needing to open either schema.

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?

'Start here for questions about the person rather than a project' gives an explicit entry-point recommendation plus an exclusion criterion (person vs. project). It stops short of naming specific siblings like answer_question or list_faqs, so routing in ambiguous cases still requires inference.

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