lexicon_raw_request

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

No annotations are provided, so the description must carry full burden. It mentions deprecation but fails to disclose behavioral traits like authentication requirements, error handling, or whether the tool is read-only or mutating. Minimal transparency.

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-loads the deprecation warning. It is efficient but lacks structured details that would improve readability. Adequate but not exceptional.

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 there is no output schema, no annotations, and only 2 parameters, the description should be more thorough. It omits important context such as response format, error scenarios, and authentication needs. Incomplete for a deprecated tool that may still be invoked.

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 should add meaning. It states 'path' is required and 'body' is a JSON object, but provides no format details (e.g., path must start with /v1/) or examples. Barely adds value over the param names.

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 that the tool makes a generic Lexicon API call and is deprecated in favor of lexicon_request. This gives agents a specific verb and resource, and the deprecation note distinguishes it from the alternative tool.

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?

Explicitly tells agents to use lexicon_request with method GET instead, and describes current usage as 'Call any Lexicon /v1 path with JSON body'. This is clear guidance for when to use this tool vs the alternative.

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