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

The annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered; the phrase "curated ... tracked by mitbbs.ai" is at least consistent with the closed-world hint. Beyond that the description adds no behavioral context: it doesn't say what happens when both q and id are supplied, whether q returns ranked or paginated results, or what a profile contains.

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 with zero filler, and the search-versus-profile fork is front-loaded immediately after the scope statement. Every clause carries information.

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 exists, so return values need not be explained, and with annotations covering safety the remaining need is a scope statement plus invocation routing — both present. The only real omission is sibling differentiation, which is a minor gap for a simple read tool with no required parameters.

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 50%: q and id already carry descriptions that essentially mirror the prose, while type (an enum) and limit (1-20, default 10) are undocumented in both places. The description restates rather than extends the schema, so baseline 3 is appropriate given the partial coverage gap.

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 states a specific verb ("look up") and a clearly bounded resource ("curated entities ... tracked by mitbbs.ai"), and it enumerates the entity kinds so the agent knows the domain. It doesn't explicitly differentiate from the closest sibling, yellow_pages, which is a plausible source of confusion for a lookup-style tool.

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?

It implies two distinct modes — pass q to search, or id (stable_id) for a profile — which is genuine routing guidance between invocation styles. However, it gives no guidance on when to reach for this tool versus yellow_pages or search_news, and no exclusion or prerequisite conditions.

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