Get Manifests by File Values

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

With no annotations, the description carries the full burden. It adds some behavioral context ('across ALL schemas', 'Returns Manifest entities directly'), but it does not disclose search behavior such as case-sensitivity defaults, result limits, or whether the operation is read-only. For a search tool, this is minimal but not misleading.

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 two concise sentences, front-loaded with the primary action and scope. Every word earns its place with no redundancy or fluff.

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 gives a clear high-level purpose and scope. While it lacks an output schema and annotations, the parameter schema is fully documented, and the description covers the key differentiator (all schemas). It could be more complete about return structure, but 'Returns Manifest entities directly' suffices for this simple search 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?

Schema description coverage is 100%, so the baseline is 3. The description does not add any parameter-specific meaning beyond what the schema already provides. It does not clarify the relationship between multiple 'file field values' and the single 'fieldValue' parameter, but the schema descriptions are sufficient.

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' and the resource 'Manifests', with explicit scope 'across ALL schemas'. This distinguishes it from siblings like get_manifests_by_schema_name_and_file_fields that are schema-scoped. The phrase 'Returns Manifest entities directly' also clarifies the return type.

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?

Usage is implied through the phrase 'across ALL schemas' but there is no explicit guidance on when to use this tool versus alternatives. No alternatives are named, nor are any exclusions or conditions mentioned.

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