List Coordination Issue File Filter Options

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, covering the safety profile. Description adds the API endpoint and that response is a JSON array, but no additional behavioral traits beyond annotations.

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?

Two sentences in first paragraph + two short sentences. Efficient but slightly repetitive: 'Returns a list...' and 'Returns a JSON array...' could be merged. Front-loaded with purpose.

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?

Moderate complexity tool with no output schema. Description explains purpose, usage scenario, required parameter, and API endpoint. Lacks details on the response structure (e.g., each filter option's fields), but for a filter options list it is reasonably complete.

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?

Input schema has 100% description coverage with clear descriptions for all 4 parameters. Description only reiterates that project_id is required and mentions pagination, adding no new meaning beyond the schema.

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 returns a list of source file filters for Coordination Issues, with specific usage context (paginated overview, find IDs, filter by query). Distinguishes from sibling tools like 'list_available_filters_for_coordination_issues' by specifying 'coordination_issue_file_id' filter.

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 context for when to use the tool (enumerate Coordination Issues with pagination, find IDs, filter by query parameters). Mentions required project_id. Does not explicitly state when not to use or compare to alternatives, but usage is well implied.

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