codex_search_chats

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

With no annotations, description discloses key behaviors: uses FTS index, returns ranked matches not full transcripts, never calls DeepSeek. It does not address rate limits or index staleness, but covers core traits well.

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 succinct sentences: first defines scope and sources, second clarifies returns and what it doesn't do. No fluff, front-loaded with key 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?

Given 11 parameters with zero schema descriptions, the description does not provide enough detail for complete tool usage. Agent would need to infer or experiment with parameters like match_mode, cursor, and refresh_index.

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 0%, and description only implicitly explains 'query' via 'keywords, multiple terms, or exact phrases'. Most parameters (match_mode, project_id, limit, etc.) are not explained, leaving gaps for the agent.

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 it searches Codex chats using FTS index, specifies verb 'search' and resource 'Codex chats', and distinguishes from getting full transcripts. It uniquely identifies its purpose among siblings.

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?

Description implies when to use (searching chats), but lacks explicit guidance on when not to use or alternatives. It mentions not calling DeepSeek but does not provide clear contrast with other tools.

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