list_my_merge_requests

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

Adds behavior that it auto-uses configured username, but lacks details on pagination, sorting, or error handling. No annotations to support.

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?

Extremely concise single sentence, front-loaded with key information, 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?

With 5 parameters and 3 required, the description is too sparse. It lacks details on parameter usage, output schema, or how filters work, making it incomplete for complex use.

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?

Description provides no explanation for any of the 5 parameters (limit, state, filters, platform, project_id), leaving agent without guidance on how to use them effectively.

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?

Description clearly states the tool lists merge requests created by the current user, with a specific verb and resource, and distinguishes from sibling 'list_merge_requests' by adding the 'my' scope.

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?

Implied usage for current user's merge requests, but no explicit when-not-to-use or mention of alternative tools like list_merge_requests.

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