get_conflicts

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only says 'Get' which implies a read operation, but it does not state whether the tool requires any permissions, what happens when the change is not conflicted, or whether the operation is safe and reversible. There is also no mention of the response format or error conditions.

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, efficient sentence with no wasted words. It is appropriately front-loaded. However, it is so terse that it could be considered under-specified rather than properly concise, so it does not earn a perfect score.

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 tool that is part of a rich conflict lifecycle (with siblings like propose_conflict_resolution, apply_conflict_resolution, and check_mergeability), the description lacks essential context. It does not explain what the returned conflict information can be used for, nor any preconditions or relationships to other tools. With no annotations or output schema, the description is insufficient for an agent to know when and how to use it correctly.

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 schema has only one parameter, change_id, with 0% description coverage. The description does not clarify what change_id refers to beyond the name itself. Although the name is fairly self-explanatory, the description fails to compensate for the lack of schema documentation, leaving the agent with no additional meaning (e.g., 'ID of the change request to fetch conflicts for').

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 states a specific verb (Get) and resource (structured conflict information for a conflicted Change Request), clearly distinguishing it from siblings like propose_conflict_resolution or check_mergeability. It is not a tautology, though it could be more precise about what 'structured' entails (e.g., conflict categories, file paths).

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention that it is the first step before proposing or applying resolutions, nor does it note constraints such as requiring a change to already be in a conflicted state. An agent must infer the intended use from the tool name alone.

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