submit_bug

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

Discloses that it returns the created bug record or None on failure, but provides no info on side effects (creation), required permissions, rate limits, or additional behavioral traits. Since annotations are absent, the description carries the full burden and falls short.

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?

Two concise sentences that state purpose and return value without redundancy. However, the extreme brevity omits critical parameter and usage details, which could be added without harming conciseness.

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 10 parameters, 2 required, and zero parameter descriptions in either schema or description, the tool is severely underdocumented. The output schema exists but is not shown; the description does not fill the gap.

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?

Schema description coverage is 0%, and the description does not explain any of the 10 parameters (e.g., title, provider_name, importance). The agent gets no help understanding what each parameter means or how to use them.

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 verb 'Submit' and resource 'new bug', and the tool's action is distinct from siblings like get_bug or search_bugs. However, it does not specify what 'provider' means or how it relates to providers.

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, no prerequisites (e.g., requires login via login_provider), and no conditions for success or failure beyond the return value.

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