get_kwork_details

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

The description adds behavioral context by listing the return data (reviews, FAQ, similar kworks), going beyond what annotations provide (readOnlyHint, idempotentHint). No contradictions 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?

The description is concise with three short sections: main statement, usage guidance, and related tool. Every sentence adds value with no waste.

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 presence of an output schema (covers return structure) and clear annotations (readOnly, idempotent), the description completes the picture by explaining the tool's specific output and use case. A model of completeness for a simple 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?

Although schema coverage is 0%, the description compensates by stating 'by its ID', clarifying that the integer parameter is the kwork's unique identifier. For a single required parameter, this provides sufficient semantic meaning 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?

The description clearly states 'get detailed information about a kwork by its ID', specifying the verb and resource. It also lists what information is returned (reviews, FAQ, similar kworks), distinguishing it from sibling tools like list_my_kworks that only return name and price.

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?

The description explicitly says 'When to use: to view reviews, FAQ, and similar kworks', providing clear guidance on when to invoke this tool. It also mentions a related tool (list_my_kworks) with its own purpose for differentiation.

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