wetrack_get_my_sprint_report

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

No annotations are provided, so the description carries the behavioral disclosure burden. It usefully discloses the report contents, the default to the user's current active sprint, and filter/pagination options. It does not explicitly state that the operation is read-only, but the 'get' name and report framing make harmful side effects unlikely.

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 short and well-structured: one informative purpose line followed by a compact Args list. Every sentence contributes useful information, and the main idea is front-loaded.

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 output schema exists and all five parameters are documented, the description is mostly sufficient for correct invocation. It could be improved by stating when to choose this over sibling report tools, but nothing essential for calling the tool is missing.

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 Args block carries the semantic weight. It explains each parameter: sprint_id as a Sprint UUID with a default, status_id and priority_id as filters, and page/limit for pagination. This adds meaningful value beyond the bare schema properties, though the filter ID formats are terse.

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 identifies the resource: the current user's My Sprint report, including progress, burndown, distributions, and ticket list. The name and scope make it distinct from other report tools, though it does not explicitly contrast siblings like wetrack_get_my_work_report.

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 implies the tool is for the current user's active sprint, but gives no explicit when-to-use guidance and does not mention alternatives or conditions for choosing a different report tool. An agent must infer usage from the name and context.

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