Ops MCP Server

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns items 'ordered by priority with state and effort,' which adds useful behavioral context beyond the input schema. However, it doesn't mention potential limitations like pagination, error conditions, or authentication requirements, leaving some gaps for a tool with no annotation coverage.

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 well-structured and front-loaded: it starts with the purpose, then usage guidelines, followed by parameter explanations. Every sentence earns its place with no redundancy. It's appropriately sized for the tool's complexity, making it easy for an agent to parse quickly.

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?

Given the tool has an output schema (which handles return values), no annotations, and 3 parameters with 0% schema coverage, the description does a good job. It covers purpose, usage, and parameter semantics adequately. However, for a tool with no annotations, it could benefit from more behavioral details like error handling or rate limits, keeping it from a perfect score.

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 adds meaning by explaining each parameter: 'project: Project name (default from config)', 'team: Team name (default from config)', and 'max_results: Maximum items to return (default 50).' This clarifies the purpose and defaults, though it doesn't provide format details or constraints. With 3 parameters, this is a strong effort that significantly enhances understanding.

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 clearly states the tool's purpose: 'Get backlog items (PBIs/User Stories not in the current sprint).' It specifies the verb ('Get'), resource ('backlog items'), and scope ('not in the current sprint'), distinguishing it from sibling tools like get_current_sprint and get_sprint_work_items. This is specific and unambiguous.

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?

The description provides explicit usage guidelines: 'USE THIS TOOL when the user asks about the backlog, upcoming work, 'what's next?', 'what's not in the sprint?', or items waiting to be picked up.' It gives clear examples of when to use this tool, helping the agent distinguish it from alternatives like get_current_sprint. No exclusions are mentioned, but the guidance is comprehensive.

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