get_active_sprint

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

Discloses it's a read operation ('Find') and explains selection criterion ('date range contains now'). No annotations, but description adequately covers behavioral traits for a simple tool.

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?

Single sentence, zero wasted text, efficiently conveys tool purpose and key logic.

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?

Complete for a simple tool: explains functionality and routing logic. Could optionally mention return type (List object) but not necessary.

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?

Single parameter folder_id with schema description 'Sprint Folder ID.' Description adds no extra meaning, but 100% schema coverage makes baseline 3 appropriate.

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 verb 'Find' and resource 'currently active sprint in a Sprint Folder', distinguishing it from sibling tools like list_sprints and get_sprint_tasks.

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?

Implies usage when needing the active sprint; could explicitly mention when not to use (e.g., for historical sprints) but contextual clarity from siblings compensates.

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