getDatabaseDeprovisionExample

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

No annotations are provided, so the description must itself convey safety and behavior. 'Gets an example' implies a read-only operation with no side effects, but it does not explicitly confirm non-destructiveness or describe the output format. The description adds some transparency but could be more explicit about what the example looks like.

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 sentence that front-loads the action ('Gets an example') and specifies the exact type of example ('GitHub Action for deprovisioning a database'). It contains no filler and is appropriately sized for the tool's simplicity.

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?

Given the tool has no parameters and an output schema exists, the description is largely sufficient. It states what the tool returns, but the output schema not being shown in the input schema means the description alone doesn't fully describe the return value. Despite this, the simplicity of the tool means the description covers most essential context.

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, so the baseline is 4. The description correctly avoids discussing parameters, as there are none. No additional semantic meaning is needed beyond the schema's empty property list.

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 a specific verb 'Gets' and identifies the resource as 'an example of a GitHub Action for deprovisioning a database'. This clearly differentiates it from sibling tools like getDatabaseProvisionExample and getDatabaseRestoreExample, making the tool's purpose unambiguous.

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 provides no guidance on when to use this tool versus alternatives. It does not mention troubleshooting, use cases, or refer to other example tools, so an agent receives no explicit context for selection.

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