fossa_get_issue_exceptions

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

Adds meaningful context beyond the readOnlyHint annotation by explaining what an exception is (scope, creator, expiry) and how it keeps issues out of the active set. No contradiction with annotations; the extra detail helps the agent understand the domain.

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?

Three sentences, front-loaded with the main purpose. Each sentence adds value: purpose, conceptual explanation, and usage pattern. No fluff or redundancy.

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?

Despite having an output schema, the tool has 9 optional parameters with zero schema descriptions. The description omits pagination, filtering, sorting, and project/release-group scoping, leaving significant gaps for an agent to invoke the tool correctly in various scenarios.

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 description coverage is 0%, so the description must compensate. It only clarifies exception_id and category, while 7 other parameters (page, count, search, sort_by, project_id, release_group_id, order_by) remain unexplained except by their names, which is insufficient for a 9-parameter tool.

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?

Clearly states it lists organization issue ignore rules or fetches one by id. The verb 'list' and resource 'issue ignore rules' are specific and distinguish it from sibling mutation tools like delete_issue_exceptions or extend_issue_exception.

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 usage guidance by noting 'Read-only' and instructing to pass exception_id for a single rule or category to list. It does not explicitly name alternative tools, but the guidance is clear enough for basic selection between list and fetch modes.

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