search-logged-models

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the description adds limited behavioral context beyond stating 'filter and pagination'. No mention of side effects, auth requirements, or rate limits. The description does not contradict 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?

A single, well-structured sentence capturing the core function. No unnecessary words. Front-loaded with the verb and resource.

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?

No output schema exists, and the description does not explain the return format or fields. For a search tool, providing only 'filter and pagination' without mentioning response structure or common fields (e.g., total count, next page token) leaves gaps. Adequate but not fully 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?

Schema coverage is 60% (some parameters lack descriptions). The description mentions 'by experiment with filter and pagination' which broadly covers experimentIds, filter, and pageToken, but does not add meaning beyond the schema. It fails to explain maxResults or orderBy in more detail. Baseline 3 with no significant compensation.

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 verb 'Search', the resource 'LoggedModels', and the key dimensions 'by experiment with filter and pagination'. It distinguishes this tool from sibling search tools (e.g., search-experiments, search-runs) by specifying the resource and 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 does not explicitly state when to use this tool vs alternatives or provide any exclusions. However, the resource name and context (looking for LoggedModels) imply its usage. No guidance on when not to use or compare to siblings.

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