Random Unbroken Seal

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

With no annotations, the description must fully disclose behavioral traits. It describes a read-like operation ('Get') but does not explicitly state that it is non-destructive, idempotent, or stateless. The user cannot tell if calling this tool changes any state or requires specific permissions.

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 a single sentence of five words, making it highly concise. It front-loads the key action and object. However, it could include a brief note on output format without significantly increasing length.

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 or annotations, the description should fully explain the return value. It only says 'location' without specifying whether it is an integer, string, or object. This omission makes the tool harder to use correctly without additional 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 tool has zero parameters and schema coverage is 100%. Baseline is 3. The description adds meaning by specifying 'random unbroken seal' but does not elaborate on the format or type of the returned location, which would have added value.

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 gets a random unbroken seal location. It specifies the verb 'Get' and the resource 'random unbroken seal location', which distinguishes it from sibling tools like tower_break_seal and tower_get_broken_seals. However, it does not define what 'location' means (e.g., coordinate or index), slightly reducing clarity.

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 usage guidelines are provided. The description does not indicate when to use this tool over alternatives, such as tower_get_broken_seals or tower_is_seal_broken. It fails to give context for when to invoke it, leaving the agent to infer its purpose from the name alone.

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