create_search_bulk

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

Annotations already indicate readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the description does not add behavioral context. It does not describe what happens on creation, the response format, or any side effects. The only extra note is about reading the schema first, which is more of a usage hint than a behavioral disclosure.

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 very short and front-loaded with the purpose ('Create Search'), followed by the endpoint URL and a concise parameter note. Every sentence earns its place. It could be slightly longer to clarify the bulk nature, but as written it is efficient and well-structured.

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 complexity (one opaque parameter and a 'bulk' name that is unexplained), the description is incomplete. It does not mention that this is a bulk operation, does not clarify how it differs from create_search, and relies entirely on the schema endpoint for payload details. The output schema is present, so return values are covered, but the operational context is lacking.

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 has a single 'body' parameter with additionalProperties:true and no description (0% coverage). The description compensates by telling the agent to read the matching GET or /schema endpoint to discover the expected fields. This is a practical workaround for the opaque parameter, though it does not provide any direct semantic detail about the parameter itself.

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 states 'Create Search.' which clearly identifies the verb and resource—creating a search object. However, it does not mention the 'bulk' aspect implied by the tool name, nor does it differentiate from the sibling tool create_search. The purpose is clear but lacks specificity about what makes this tool distinct.

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 instructs the agent to 'Read the matching GET or the /schema endpoint first to see the fields this resource expects.' This is a useful prerequisite but does not address when to use this tool versus alternatives like create_search, nor does it specify any conditions or exclusions. There is no guidance on when a bulk create is appropriate.

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