YOUR_TOOL_NAME

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

There are no annotations, and the description offers no behavioral details such as side effects, permissions, rate limits, or return behavior. The description is an empty placeholder, so the agent gets no transparency about what happens when the tool is invoked.

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?

While the text is extremely short, this is not conciseness but under-specification. A single placeholder sentence conveys no information, similar to the 'process' example. There is no structure, no front-loading, and no useful content.

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 has one parameter, no output schema, and no annotations, the description needs to carry all contextual weight. It provides nothing, making the tool completely opaque to an AI agent. The context is entirely missing.

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 one required parameter 'query' with type string and no description, yielding 0% schema description coverage. The description does not compensate by explaining the parameter's meaning, format, or acceptable values, leaving the agent completely uninformed about how to fill the parameter.

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 is the literal placeholder 'YOUR_TOOL_DESCRIPTION', which does not state any verb, resource, or functionality. It fails to distinguish this tool from siblings like web_search or roll_dice, providing zero information about what the tool does.

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. There is no mention of context, prerequisites, or circumstances that would favor this tool, leaving the agent with no basis for tool selection.

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