jira_default_board_id

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

No annotations exist, so the description must bear full burden. It mentions routing and scope but provides no information on whether the tool is read-only, destructive, or has side effects. The behavior is completely opaque.

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 wastes words by repeating the tool name and platform reference. The three sentences could be condensed into one without loss of information. It is not optimally concise.

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?

The tool has a generic parameter and no annotation support. The description is incomplete: it does not explain the return value (despite an output schema existing), error conditions, or how to construct arguments. An agent cannot use this tool correctly based on this description.

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 described as a 'JSON string of arguments for the connector operation,' which adds minimal meaning. With 0% schema description coverage, the description should specify expected keys or structure, but it does not.

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 merely restates the tool name ('Jira connector operation `default_board_id`') without specifying what the tool does. It does not indicate that it retrieves the default board ID, leaving the agent without a clear purpose.

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 is provided on when to use this tool versus alternative Jira tools. With many sibling Jira tools, the lack of differentiation makes it impossible for the agent to decide when to invoke this one.

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