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

With no annotations, the description must carry the full behavioral burden, but it states nothing about side effects, safety, permissions, rate limits, or what a successful search actually returns. The phrase 'what you pay' is the only behavioral hint and it is ambiguous.

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, but brevity here comes from under-specification rather than efficient delivery of useful information. It is a slogan, not a structured tool description.

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?

Despite a simple one-parameter schema, the description is not complete: it omits the tool's actual purpose, return behavior, and relationship to chamber_get and sibling search tools, and there is no output schema to compensate.

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 only documents q as an optional string, and schema description coverage is 0%. The description's 'Free text or code' adds minimal meaning to q, but it is too vague to tell an agent what kinds of queries are valid or how to format them.

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 'Chamber — what it is, what you get, what you pay' gestures at an informational search tool but never names a verb, a resource, or a clear operation. It does not distinguish chamber_search from chamber_get or any sibling.

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?

There is no guidance about when to use this tool instead of chamber_get or the other *_search tools. 'Free text or code' hints at input format, not a selection criterion.

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