Get Affected Body Part Filter Options

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true. The description adds only redundant information (required params, endpoint) and does not disclose any behavioral traits beyond what annotations provide.

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 4 sentences. The second sentence about fetching incident details is irrelevant and should be removed. The remaining information is concise but not perfectly structured.

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?

No output schema exists, so the description must compensate. It states 'Returns a JSON array of available filter values for Incidents', which gives a basic idea. However, it does not mention pagination behavior for 'page' and 'per_page' parameters, leaving an incomplete picture for a tool with 3 parameters.

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 100%, so baseline is 3. The description adds endpoint context ('GET /rest/v1.0/projects/{project_id}/incidents/injuries/filter_options/affected_body_parts') which clarifies how project_id is used, but no further semantic value is added.

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 'Returns affected body parts in use for filtering injuries', which is clear, but then contradicts by saying 'Use this to fetch the full details of a specific Incidents by its identifier', which is inaccurate for this tool. This conflict degrades clarity and may mislead an agent.

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 explicit guidance on when to use this tool versus alternatives (e.g., 'get_affected_body_parts'). The misleading instruction about fetching incident details adds confusion rather than clarifying usage context.

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