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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds one meaningful trait beyond that — results are 'cited', i.e. they carry provenance — but says nothing about ranking, matching behavior, or what happens when no topics match.

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?

A single front-loaded sentence with no filler; the verb and resource lead and the domain list follows. It is efficient, though the comma-spliced domain list gets slightly listy without structure.

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?

An output schema and rich annotations relieve the description of explaining return values and safety, and the domain list covers scope. What remains missing is the disambiguation from heavily overlapping siblings and any documentation of the three undescribed parameters, which is a meaningful shortfall for a search tool in a crowded namespace.

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 0% across three parameters, so the description carries the full burden and largely fails: query syntax, what the limit caps, and especially what values belong in `topics` (free strings? these domain names?) are never addressed. The enumerated domains loosely hint at valid topics values, which is the only partial compensation.

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 ('Searches') plus the resource ('cited first-party context') and enumerates the topical domains covered (career, projects, Ephemera Digital Collection, donations, Portfolio MCP setup, contact facts). An agent can tell what it returns, but the description never contrasts it with the obviously overlapping siblings get_first_party_context, search_project_notes, and fetch_curated_page_context.

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 only implied through the topical enumeration — the agent can infer when the tool is relevant but is given no when-to-use rule, no exclusions, and no named alternative. With three sibling search/context tools in the list, the absence of routing guidance is a real gap.

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