Describe JobBOSS2 resource

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

Annotations already provide readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds that the tool returns paths, keys, query parameters, and request schema, which is useful but not deep behavioral disclosure such as resource naming/pagination or operation-specific behavior. No contradiction with annotations.

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 with no filler. The main capability is front-loaded, and the usage directive is preserved for the second sentence. Every word adds value.

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?

For an introspection tool with an output schema and read-only annotations, the description covers the core capability, what the agent can inspect, and when to call it. The only minor gap is that it does not spell out how the optional operation parameter changes the behavior between listing resources and inspecting one resource.

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%, so the description must compensate. It implies the 'resource' parameter selects which resource to inspect and that 'operation' relates to the intended create/update/get/list action through the phrase 'before create or update tools.' However, it does not explicitly explain the operation parameter's behavior or default when omitted, leaving some burden on the enum values in the schema.

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 identifies the tool as an introspection/metadata tool: it 'List JobBOSS2 resources or inspect one resource's paths, keys, query parameters, and request schema.' This distinguishes it from the actual data-operation siblings (create, update, list, get) and explains exactly what the agent will learn by calling it.

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 gives explicit guidance on when to call it: 'Call this before create or update tools.' This is a clear usage context. It does not explicitly list exclusions for other siblings, but the purpose is distinct enough that the guidance is sufficient.

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