fossa_delete_jira_configuration

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

Annotations already indicate destructive and write operations. The description adds valuable context: stored credentials are deleted, issue tracking is severed, and the id vs name pitfall is highlighted. This goes beyond the annotation flags.

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 concise, front-loaded with the core action, and each sentence adds essential information: side effects, prerequisites, and a practical tip. No wasted words.

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 simple one-parameter delete tool with an output schema, the description covers side effects, prerequisites, and a common confusion point. It could mention reversibility explicitly, but the annotations and context make this acceptable.

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 low (0%), but the description clarifies the only parameter (jira_id) by noting it is not the Jira site name and suggesting to list configurations first. This meaningfully compensates for the schema's minimal title.

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 explicitly states the action 'Delete a Jira site configuration', which is a specific verb and resource. It clearly distinguishes from sibling tools like get_jira_configurations and save_jira_configuration by naming the operation.

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?

Provides clear guidance that this writes to FOSSA and requires env vars, and advises listing sites first because the id is not the Jira site name. It doesn't explicitly mention alternatives, but the tool name and context make the use case clear.

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