stock_token_terms

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

With no annotations, the description must convey behavioral traits. It mentions security restrictions but does not specify if the tool is read-only, whether it requires authentication, or what happens if the token is not a valid stock token. The behavior is implied but not explicit.

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 concise with two sentences, each adding value. The first sentence states the core functionality, and the second provides necessary legal context. No extraneous 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?

For a simple one-parameter tool, the description is adequate but lacks details on error handling, return format, or behavior when the token is invalid. Given no output schema, the description should compensate more fully.

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 sole parameter 'token' has no description in the schema (0% coverage), and the description does not clarify its format (e.g., address, symbol) or provide examples. This leaves the agent guessing about valid inputs.

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 identifies the tool as retrieving a legal terms URI for a stock token, including context about the issuer and restrictions. However, it lacks an explicit action verb like 'Retrieve', which would improve clarity. The purpose is sufficiently distinct from sibling tools such as stock_token_info or verify_stock_token.

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 like stock_token_info or verify_stock_token. There is no mention of prerequisites, contexts where it should be avoided, or when the tool might fail (e.g., invalid token).

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