Show Standard Cost Code

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

Annotations already indicate read-only, non-destructive, idempotent behavior. The description adds that it returns a JSON object, which is expected but minimal. 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?

The description is four sentences covering purpose, usage, required parameters, and API endpoint. It is front-loaded with the key action and resource, with no redundant information, making it efficient.

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 a show endpoint with no output schema, the description adequately states it returns a JSON object with full details. However, it could be more complete by specifying common response fields or providing an example, especially given the tool has 6 parameters and no output schema.

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 100%, so baseline is 3. The description merely repeats the required parameters (id, company_id, standard_cost_code_list_id) without adding any additional meaning, format constraints, or relationships beyond what the schema provides.

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 the tool returns information about a specific Standard Cost Code using its identifier, referencing the Work Breakdown Structure. It identifies the resource and endpoint, but does not explicitly differentiate from other 'show' siblings like show_standard_cost_code_list or show_cost_code.

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 says to use this tool to fetch full details of a WBS record by identifier and lists required parameters. However, it does not provide when-not-to-use guidance or mention alternative tools for related operations, such as listing all standard cost codes.

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