stock_token_registry

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

With no annotations, the description carries full burden but only mentions the data it provides (address, pause state, role). It does not disclose whether the tool is read-only, requires authentication, or has side effects. The behavioral traits beyond the listed data are absent.

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 two concise sentences, front-loaded with the core identity and function. Every word adds value, with no redundancy or filler.

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 no output schema and no annotations, the description should more thoroughly explain the return format, but it only vaguely mentions 'address, pause state, and its role'. It lacks specifics about the structure of the response, error cases, or what 'its role' means. The beacon role is noted but not elaborated.

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?

There are no parameters, and the schema coverage is 100%, so baseline is 4. The description adds no parameter-specific information because none exist, which is appropriate. It does not need to elaborate on absent parameters.

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 identifies the tool as the Stock Token AccessControlsRegistry and states it provides address, pause state, and role, plus acts as a beacon. This gives a clear resource and function, though it lacks an explicit verb like 'get' or 'retrieve', making the action slightly implied. It distinguishes from siblings by its specific domain.

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 such as stock_token_info or verify_stock_token. The description only states what the tool is, not when it is appropriate.

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