baron_issue_read

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

Describes the output for get (one normalized issue), query (filtered list), and iterations (sprints with current flag). Mentions allowed special values like '@me' and '@current'. However, the 'classify' operation is absent, and no side effects, error conditions, or rate limits are disclosed.

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 a single sentence with a clear front-loaded purpose ('Read work items') and structured enumeration of operations. It is concise but could be better organized (e.g., bullet list) and is missing the 'classify' operation.

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 7 parameters, no output schema, and no annotations, the description covers the main operations well but omits the 'classify' operation entirely. It also lacks details on pagination, error handling, or authentication needed for a fully complete profile.

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?

With only 14% schema description coverage, the description adds significant meaning: it associates parameters with operations (e.g., id for get, role/typeRole/assignee/iteration/limit for query) and explains special values. However, the 'classify' operation's parameters are not described.

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?

Clearly states the tool reads work items and details three operations (get, query, iterations) with their specific actions. However, the 'classify' operation from the schema is not mentioned, leaving its purpose unclear.

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 reading via the phrase 'Read work items' and the sibling tools indicate write/move variants. No explicit guidance on when to use or when not to use this tool, nor alternatives are named.

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