Get anyCreature availability

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds valuable behavioral context beyond those: it does not start a browser and does not request credentials, which clarifies that this is a lightweight, non-interactive status check. No contradiction with annotations.

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, front-loaded sentence with no filler. However, terms like 'pinned anyCreature payload' and 'optional local tooling' are somewhat jargon-heavy and may require the reader to infer their meaning.

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?

With no parameters, an output schema present, and annotations covering safety, the description provides adequate context: purpose, non-interactive nature, and credential-free operation. It is reasonably complete, though it could clarify what 'optional local tooling' refers to.

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 the empty schema has 100% description coverage, so the baseline is 4. The description does not need to elaborate on parameters; none exist.

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 uses the specific verb 'Report' and names the resource ('pinned anyCreature payload') and the exact content reported (payload, currently available operations, optional local tooling). This clearly distinguishes it from sibling tools that search, import, or inspect assets.

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?

The description implies when it should be used: when you need status/availability information without the overhead of a browser or credentials. However, it does not explicitly state when to use this tool versus alternatives like creature_guide or asset_inspect_rig, and it offers no exclusions or conditions.

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