baron_native_request

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

No annotations exist, so the description must disclose all behavioral traits. It states that Baron attaches base URL + auth and caps response size, and that the call is non-portable. However, it omits details on error handling, potential destructive side-effects (since METHOD can be DELETE/PATCH), or response format. More disclosure would be needed for complete transparency.

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 compact (3 sentences) and front-loaded with the key concept 'ESCAPE HATCH'. Every sentence serves a purpose: stating what it is, when to use, and what the user provides vs what Baron handles. No fluff.

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 5 parameters (3 required), no output schema, and nested objects. The description explains the high-level flow and constraints but does not detail what the response looks like (beyond 'size-capped'), error responses, or format of body/query parameters. For an escape hatch, some missing details may be acceptable but the response shape is left ambiguous.

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 coverage is 80% (4 of 5 parameters have descriptions). The description adds meaning by explaining that the user supplies the provider-native method+path+query/body and that Baron only adds the base URL and auth. It reinforces the role of each parameter in the tool's execution, going beyond the schema's brief descriptions.

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 explicitly states 'raw, authenticated, NON-PORTABLE provider REST call' and positions itself as an 'ESCAPE HATCH — last resort' contrasting with the normalized sibling tools (issue/scm/ci/notify). This clearly distinguishes the tool's purpose from the sibling list.

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?

It provides explicit when-to-use ('Last resort for when no normalized tool covers the need') and when-not-to-use ('Prefer the normalized tools — this is provider-specific and will not port'). It also mentions constraints: 'Only providers bound in the active policy are reachable.' This gives the agent clear guidance on alternatives and limitations.

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