manage_issues

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

The description does not mention any side effects, destructive potential, or irreversible actions. Since actions like 'create' and 'delete' (implied by 'manage') may have significant consequences, the lack of warning is a transparency gap. No annotations compensate for this omission.

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 concise and well-structured, listing actions in a clear format (action = list | create | ...). It avoids unnecessary words, making it easy to parse, though it could benefit from a brief explanation of each action.

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?

With no output schema and no parameter descriptions, the tool is incomplete. The description does not clarify expected inputs for each action, return values, or error conditions, making it insufficient for reliable execution without external documentation.

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 description provides no information about the seven parameters (name, port, guids, action, comment, bcf_path, issue_id). The schema lists types but no explanation of their purpose or relationships, leaving the agent to guess how to fill them for each action.

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 states the tool's purpose as managing Archicad issues and enumerates the possible actions (list, create, comment, attach, export, import). This distinguishes it from other tools like delete_elements or get_project_info, though it doesn't elaborate on each action's function.

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?

There is no guidance on when to use this tool compared to alternatives. It does not indicate scenarios where issue management is appropriate or how it relates to other operations, leaving the agent without situational context.

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