Gibwork List Bounties

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

Description contradicts annotations: annotations set readOnlyHint=true, but description says 'operation class write' and 'Use for bounty creation' implying write behavior. This is a serious inconsistency.

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 has two sentences, but the second is a long run-on that mixes unrelated guidance, reducing clarity. Could be more concise and front-loaded.

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 an output schema present, the description fails to explain what the tool returns (list of bounties) or any notable behavior. The SAP context is confusing and unnecessary for understanding the tool.

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 descriptions for parameters are tautological (e.g., 'Tags parameter for Gibwork List Bounties') and add no real meaning. The tool description does not provide any additional parameter guidance beyond 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?

First sentence clearly states 'List available bounties on Gib Work,' but the following sentence muddles purpose by claiming 'Use for bounty creation, listing, and work submission,' which incorrectly attributes write operations to a read-only tool.

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 explicit guidance on when to use this tool vs sibling tools like gibwork_createBounty or gibwork_submitWork. The mention of 'SAP attestation or feedback tools after work completion' is vague and not directly helpful for selecting this tool.

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