jira_start_sprint

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

Without annotations, the description should disclose behavioral traits. It only mentions routing details (JWT, tenant, company scope) which are generic. It does not explain side effects (e.g., issues are moved, sprint becomes active) or requirements (permissions, state constraints).

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 very short, but not particularly informative. It is concise but at the expense of providing meaningful guidance. The structure is straightforward but does not earn its place with valuable content.

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 complexity of starting a sprint (requires inputs like sprint ID, likely affecting issues and dates), the description is incomplete. The output schema exists but does not compensate for the lack of input specification. Siblings like jira_create_sprint and jira_add_to_sprint create confusion without clear differentiation.

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?

The single parameter 'arguments' is a JSON string with no explanation of its structure. Schema coverage is 0%, and the description only says 'JSON string of arguments for the connector operation.' The agent cannot determine what fields are required (e.g., sprint ID, name, dates).

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 mentions it's a Jira operation to start a sprint, but the purpose is vague. The exact function (start a sprint) is implied but not explicitly stated with clear verb-resource phrasing. It does not differentiate from siblings like jira_create_sprint or jira_close_sprint.

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?

No guidance on when to use this tool versus alternatives. There is no mention of prerequisites (e.g., sprint must exist, not already started) or when not to use it. The description provides no context for decision-making.

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