list_series_lookup

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the read-only nature is covered. However, the description adds no behavioral context beyond 'Read SeriesLookup'; it doesn't explain what the operation actually does, what the response contains, or anything about the lookup behavior. With annotations present, the description still fails to add meaningful behavioral 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 extremely short, but this is under-specification rather than conciseness. It lacks a full explanatory sentence; it reads more like a technical stub. There is no front-loading of key purpose or usage information, and the structure is minimal and unhelpful.

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?

For a tool with one optional parameter and an output schema, the description should at least state what the tool does and when it's appropriate. It provides almost none of that. An agent cannot infer the intended use case or the meaning of the term parameter from this description. The existence of an output schema doesn't compensate for the missing purpose and usage context.

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 0% description coverage for the only parameter (term), so the description must compensate. It only says 'term: Query parameter', which adds no semantic meaning. It doesn't explain what the term represents (e.g., a search string), its format, or its effect on results. This is nearly useless for an agent.

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 a verb ('Read') and a resource ('SeriesLookup'), and includes the term parameter, which implies this tool performs a lookup by term. However, it never explicitly states that it searches or returns series matching the term, nor does it differentiate from sibling tools like list_series. The purpose is only vaguely implied, not clearly defined.

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 given on when to use this tool versus alternatives. The description simply provides the endpoint and parameter, but doesn't mention any conditions, prerequisites, or exclusions. An agent has no information to decide between this and other list_* tools.

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