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

The description indicates a reporting action but does not explicitly state side effects such as creating a persistent record or sending a notification. The annotations (readOnlyHint=false, idempotentHint=false, destructiveHint=false) provide no additional clarity. Since the description lacks explicit behavioral disclosure, it only partially meets transparency expectations.

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: a clear purpose statement, a usage condition, and a brief explanation of priority. It avoids unnecessary detail and is easy to parse.

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 tool has 7 parameters and no schema descriptions, the description should cover all parameters to be complete. It only addresses priority and description, leaving 5 parameters unexplained. Additionally, it does not mention the output schema, though that may be less critical. The incomplete parameter coverage makes the tool hard to use correctly.

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 schema has 7 parameters with zero descriptions, and the tool description only explains 'priority' (1-10 scale) and gives guidance for 'description' (what to include). The other parameters (title, node_type, workflow_id, error_message, priority_justification) remain unexplained, leaving significant ambiguity for the agent.

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: 'Report a bug encountered while building or running a workflow.' It specifies the action (report), the object (bug), and the context (building/running a workflow). This is sufficient to distinguish it from sibling tools like request_feature.

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?

Explicit guidance is provided on when to use the tool: 'Use this when you encounter an error, unexpected behavior, or something that doesn't work as expected.' It also instructs on what to include, giving clear conditions for invocation.

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