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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety needs no restating. The description goes beyond them by disclosing the result cap ('up to 8 matches'), ordering ('best first'), per-result fields (type, title, snippet, link), and the empty-result behavior — exactly the operational traits an agent needs to interpret output.

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?

Four sentences, each doing distinct work: capability, return contract, usage context, sibling routing. It is front-loaded with the capability and the trailing sibling list is compressed into parallel clauses rather than prose.

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 single-parameter search tool with no output schema, the description supplies the return shape, ranking, result limit and empty-result case, plus routing to the other nine tools. Nothing material is missing for correct invocation or interpretation.

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 query parameter's own description already documents case handling, punctuation, prefix matching, title weighting, exact-phrase boosting and examples. The prose description adds no query semantics beyond that, so the baseline of 3 applies.

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 opens with a specific verb and resource ('Search everything in Shlok's portfolio') and enumerates the content types covered (projects, experience, leadership, education, patents, awards, certifications, community work, blog posts). It explicitly distinguishes itself from get_project, list_projects, get_experience and get_achievements, so an agent can route without opening any 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?

It states the positive condition ('specific questions the other tools don't answer directly, such as where he used a technology or whether he has done something') and then names four concrete alternatives with the condition that selects each. Both when-to-use and when-to-use-something-else are covered.

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