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

With no annotations, the description carries the transparency burden. It discloses 'read-only' which is a useful behavioral trait, but nothing else—no return format, error behavior, or dependencies. The truncated ending fails to describe the return value, which is a significant gap.

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 incomplete sentence ending with 'Returns the', which is a structural defect. It is not concise in a helpful way—it is simply truncated and fails to deliver a complete thought.

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?

Despite the tool being simple with one parameter and an output schema, the description is incomplete. It cuts off before explaining the return value, offers no usage context, and lacks any behavioral details beyond read-only. This is inadequate for an agent to reliably invoke the tool.

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 schema only defines job_id as a string with 0% description coverage. The description adds that the tool reads 'by id', clarifying that job_id is the identifier of a request/job, but it does not explain the format, source, or how to obtain it.

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 reads the status of an ENA AI request/job by id, using a specific verb (read) and resource (status). However, the sentence is truncated mid-thought ('Returns the'), which slightly undermines clarity, and the term 'ENA AI' is ambiguous without context.

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?

There is no explicit guidance on when to use this tool versus alternatives like animica_ai_ask. The read-only hint implies it's for checking status, but no direct comparison or exclusions are provided.

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