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

With no annotations provided, the description carries full burden. It discloses key behavioral traits: it's a search operation (implied read-only), returns separate result arrays, and mentions the limit constraint (max 100). However, it doesn't cover important aspects like authentication requirements, rate limits, pagination, or error conditions.

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?

The description is perfectly structured and front-loaded: purpose statement first, then parameter explanations, then return format. Every sentence earns its place with zero wasted words. The bullet-point style for Args and Returns enhances readability without sacrificing conciseness.

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 3 parameters with 0% schema coverage and no annotations, the description does an excellent job explaining parameters and return format. The existence of an output schema reduces the need to detail return values. However, for a search tool with no annotations, it could benefit from mentioning performance characteristics or result ordering.

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?

With 0% schema description coverage, the description compensates well by explaining all three parameters: 'query' (required search query), 'type' (limit to documents/emails or both), and 'limit' (max results per type with default and maximum). It adds meaningful context beyond the bare schema, though it doesn't specify the exact format for the 'type' parameter values.

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 purpose with specific verb ('Search') and resources ('documents AND emails simultaneously'), distinguishing it from siblings like 'search_documents' (documents only) and 'search_persons' (different resource). It explicitly mentions full-text search capability.

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 provides clear context for when to use this tool (searching across both documents and emails) and includes guidance on the 'type' parameter to limit to specific resource types. However, it doesn't explicitly state when NOT to use it versus alternatives like 'search_documents' or 'search_persons'.

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

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

With no annotations provided, the description carries the full burden. It discloses that the tool retrieves data (implied read-only behavior) and lists the types of information returned, which adds useful context. However, it lacks details on error handling, rate limits, or authentication needs, leaving some behavioral aspects unclear for a tool with no annotation support.

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?

The description is well-structured and front-loaded with the core purpose, followed by details on returns and parameters. Every sentence adds value: the first states the action and key input, the second lists output details, and the third clarifies parameter usage with examples. There is no wasted text, making it highly efficient.

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 tool's low complexity (1 parameter, no nested objects) and the presence of an output schema, the description is largely complete. It covers the purpose, parameter semantics, and output content adequately. However, with no annotations, it could benefit from more behavioral context like error cases or data freshness, slightly reducing completeness.

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 coverage is 0%, so the description must compensate fully. It clearly explains the 'slug' parameter as 'the person's URL slug' and provides concrete examples ('bill-clinton', 'ghislaine-maxwell'), adding essential meaning beyond the bare schema. This effectively documents the single parameter's purpose and format.

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 specific action ('Get full detail for a specific person'), identifies the resource ('person'), and distinguishes it from siblings by focusing on individual retrieval rather than search operations like 'search_persons' or 'cross_search'. It explicitly mentions what information is returned, making the purpose distinct and comprehensive.

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 provides clear context for when to use this tool: when you need detailed information about a specific person identified by their URL slug. It implies an alternative by mentioning sibling tools like 'search_persons' for broader searches, but does not explicitly state when not to use it or compare directly with all alternatives, keeping it at a 4.

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

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

With no annotations provided, the description carries full burden and does well by specifying full-text search (FTS5), pagination behavior (defaults and max), and return format. It doesn't mention rate limits or authentication needs but covers core behavioral aspects adequately.

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?

Well-structured with purpose statement followed by organized parameter and return sections. Every sentence adds value with no wasted words, and key information is front-loaded.

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?

The description is quite complete for a search tool with 5 parameters and no annotations. It explains parameters thoroughly and mentions the return format. With an output schema present, it doesn't need to detail return values further. Minor gap: no explicit mention of authentication or error handling.

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?

With 0% schema description coverage, the description fully compensates by explaining all 5 parameters with clear semantics, examples, defaults, and constraints. It adds substantial value beyond the bare schema.

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 searches Epstein case documents using full-text search (FTS5), specifying both the action (search) and resource (Epstein case documents). It distinguishes from siblings like search_flights and search_persons by focusing specifically on documents.

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 for searching Epstein case documents but doesn't explicitly state when to use this tool versus alternatives like cross_search. It provides filtering parameters but no guidance on tool selection context.

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

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions pagination behavior (page, per_page with max 100) and the return format, but doesn't cover important aspects like rate limits, authentication requirements, error conditions, or whether this is a read-only operation. Significant gaps remain for a tool with 6 parameters.

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?

The description is well-structured with clear sections for purpose, arguments, and returns. Every sentence adds value: the first establishes scope, the args section documents all parameters with useful examples, and the returns section clarifies output format. No wasted words.

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 search tool with 6 parameters and no annotations, the description does an excellent job covering parameters and return format. The presence of an output schema reduces the need to explain return values in detail. Minor gaps remain in behavioral aspects like rate limits or error handling, but overall it's quite complete.

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 description provides comprehensive parameter documentation with clear examples (e.g., '2002', 'TIST', 'Palm Beach'), default values, and constraints (max 100 for per_page). With 0% schema description coverage, the description fully compensates by explaining all 6 parameters in detail beyond what the bare schema provides.

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 searches flight logs from 1997-2006 across all known aircraft, with a specific verb ('search') and resource ('flight logs'). It distinguishes itself from siblings like search_documents or search_persons by focusing exclusively on flight data.

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 for flight log searches within the 1997-2006 timeframe but doesn't explicitly state when to use this tool versus alternatives like cross_search or get_person. No exclusions or specific contexts are provided beyond the date range.

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

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions pagination behavior (defaults and max) and the return format (JSON with specific fields), which is helpful. However, it doesn't cover important aspects like rate limits, authentication requirements, error conditions, or whether this is a read-only operation (though 'search' implies it).

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?

The description is well-structured with clear sections (purpose, args, returns) and uses bullet-like formatting. Every sentence adds value, though the category enum list is somewhat lengthy but necessary for completeness. It could be slightly more concise in the opening statement.

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 tool's moderate complexity (4 parameters, no annotations, but with output schema), the description does a good job. It explains parameters thoroughly and mentions the return format, though it doesn't fully describe behavioral aspects like error handling. The output schema existence reduces the need to detail return values, but more behavioral context would help.

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%, so the description must fully compensate. It provides complete documentation for all 4 parameters: name (full/partial search), category (with explicit enum values), page (default), and per_page (default and max). This adds substantial meaning beyond the bare schema.

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 specific action ('Search') and target resource ('Epstein files for persons of interest'), distinguishing it from sibling tools like search_documents or search_flights that search different data types. The verb+resource combination is precise and unambiguous.

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?

No guidance is provided on when to use this tool versus alternatives like get_person (for retrieving a specific person) or cross_search (purpose unknown). The description only states what the tool does, not when it's appropriate relative to other available tools.

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