create_search_recent

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

Annotations already signal non-read-only, idempotent, and non-destructive behavior, so the description needs to add behavioral context. It only adds the endpoint and a request-payload note, with no mention of side effects, authentication, or what happens on repeated calls. This does not contradict annotations but also does not enrich them.

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 short and front-loaded, with the action and endpoint stated first. The Args section is minimal but purposeful, and no filler or redundant schema repetition is present.

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 tool has an output schema, so return-value details are not required. However, the body is an open object with no inline field documentation, and the description depends entirely on an external /schema lookup. It also omits broader context about how recent searches relate to the sibling search endpoints.

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%, so the description must compensate. It identifies 'body' as the request payload and directs the agent to the matching GET or /schema endpoint to discover expected fields. This is helpful, but the description still does not explain the actual fields or any body structure.

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 'Add recent search' uses a specific verb and resource, and the endpoint 'POST /search/recent/' confirms it is a create operation. It is distinguishable from the sibling create_search_recent_remove, though it does not explain what a 'recent search' semantically contains.

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 instruction to read the matching GET or /schema endpoint is a useful how-to for body construction, and the action implies when to use the tool. However, there is no explicit guidance about when this tool should be preferred over sibling search-related tools or what the alternative conditions are.

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