Manage Automation

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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description adds almost nothing beyond that: it doesn't say whether delete is permanent or reversible, what happens to runs/history of a deleted workflow, whether permissions beyond project access are needed, or that list/get are safe reads.

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?

Two short sentences with the resource and the operation list front-loaded, and the dispatch hint immediately after. No filler or repetition of the title.

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?

This is a mixed read/write tool containing a destructive operation, with no output schema and two undocumented parameters. The description should clarify per-action parameter requirements and deletion consequences; without that, an agent cannot confidently call get_workflow or delete_workflow.

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?

Schema coverage is only 33%: `action` is documented in the schema, but `projectId` and `workflowId` have no descriptions anywhere. The description mentions 'of a GitHub project' hinting at projectId, but never states which identifier each action requires (workflowId for get/delete). With two-thirds of parameters undocumented, it fails to compensate.

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?

States a clear verb and resource ('Manage Project Automations') and enumerates the three operations (list, get, delete) with scope limited to a GitHub project's automation workflows. It doesn't differentiate this from the sibling manage_workflows, so an agent could plausibly confuse the two GitHub workflow concepts.

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 tells the agent to use the `action` field to select the operation, which is implied dispatch guidance, but there is no when-to-use, when-not-to-use, or alternative routing versus manage_workflows or manage_project. The agent must infer all selection logic from the enum.

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