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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'Get details' implying a read-only operation, but does not disclose any side effects, error handling, authentication requirements, rate limits, or what happens if the ID is invalid. This is a significant gap for a tool with zero annotation coverage.

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 concise sentence that is front-loaded with the action and resource. It avoids unnecessary words and is easy to parse. However, it is so terse that it sacrifices essential context, so while structure is clean, it is not as informative as it could be for a tool with no other documentation.

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 get-by-ID tool with one parameter, no output schema, and no annotations, the description is incomplete. It does not describe the return format, the breadth of 'details', error cases, or any prerequisites. An agent cannot fully predict the tool's behavior or response, making it inadequate for reliable invocation.

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 has one parameter, automation_id, with no description, and schema description coverage is 0%. The description says 'by ID' but does not explain what the ID represents, how to obtain it, or any constraints (e.g., integer format, required). It adds minimal value beyond the schema's bare type and required flag.

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 action (Get details) and the resource (a specific automation by ID). It distinguishes from sibling tools like list_automations (which lists all) and get_automation_log (which gets logs), so an agent can infer the basic purpose. However, it does not explicitly specify what 'details' includes or how it differs from other get tools, so it stops short of a 5.

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. There is no mention of using list_automations to find IDs, or get_automation_log for logs, or when a full detail fetch is appropriate. An agent must infer usage from the name and siblings, which is insufficient.

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