Identify integer sequence (OEIS)

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

Description adds behaviors beyond annotations: exact match, no fuzzy scoring, and honest UNDETERMINED if data absent. Annotations already indicate read-only and idempotent, which description aligns with.

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?

Two concise sentences: first states core behavior and constraints, second gives usage guidance and parameter summary. No redundant information.

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 presence of an output schema, the description adequately covers purpose, usage, behavior, and parameter hints. It is complete for the tool's complexity.

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 100%, but description adds the key constraint that terms should have >=4 integers and mentions default for max_results, providing extra context beyond the schema.

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 the tool matches an integer sequence against a local OEIS copy using exact contiguous term-match. It distinguishes from sibling 'identify_constant' by focusing on sequences, and includes specific verbs and resources.

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 states when to use: when having >=4 integer terms wanting the named sequence. The condition of data file absence leading to UNDETERMINED is mentioned. Does not explicitly exclude alternatives, but the context is clear.

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