inspect_task_definition

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

No annotations are provided, so the description must disclose safety, side effects, and return behavior. It only says 'Inspect a task definition,' which is a restatement. There is no mention of read-only nature, data volume, or any other behavioral characteristic.

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 only four words, which is extremely under-specified. While it is concise, it lacks any useful structure or front-loaded key information that would help an agent. It is a tautology rather than a meaningful description.

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?

Although there is an output schema, the description is incomplete for a task that has two required parameters and no annotations. The description fails to explain what the tool does beyond the name, and does not account for the need to specify region and task definition.

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 input schema has 2 parameters (region, task_definition) with zero description coverage. The description does not explain what these parameters mean, their format, or how they relate to the inspection. Since schema coverage is 0%, the description must compensate but does not.

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 'Inspect a task definition' is essentially a tautology of the tool name. It provides no additional detail about what aspects of the task definition are inspected or what the output represents. It does not distinguish from sibling tools like inspect_ecs_service_events or inspect_target_health.

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 mention of when to use this tool, what parameters are required, or how it differs from sibling tools like investigate_ecs_service or search_service_logs. The description provides no context for selection.

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