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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint: false. The description adds meaningful scope: 'opted-in public' and 'writer-approved', clarifying that results are limited to opted-in/public data. It also mentions compatibility with ChatGPT deep research, which hints at integration context. No contradictions with annotations.

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 concise sentences. The first states the core purpose, the second adds context about compatibility. No fluff or redundant phrasing. Every word serves a purpose.

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?

Given the simplicity of the tool (single parameter, no output schema, rich annotations), the description is complete. It defines the scope (public/opt-in), the type of content searched, and the intended context (deep research/company knowledge). No critical information is missing for an agent to select and invoke the tool.

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 description covers 100% of the parameter, listing specific searchable entities (writers, projects, genres, formats, accolades, etc.). The tool description adds no new parameter-level detail beyond what the schema provides, so the baseline score of 3 is appropriate.

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 clearly states the tool's function with a specific verb and resource: 'Search opted-in public writer profiles, project summaries, and writer-approved public assets.' This distinguishes it from sibling tools like find_projects or find_writers, which are more targeted. The inclusion of 'public' and 'writer-approved' adds clarity about scope.

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 description implies usage through the search scope and 'Compatible with ChatGPT deep research and company knowledge,' suggesting it is for open-ended discovery. However, it does not explicitly state when to prefer this tool over siblings like find_projects or get_writer_profile, nor does it provide exclusion criteria. Usage is implied rather than directly guided.

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