Show An Async Job For A Company

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds the API endpoint and notes it returns a JSON object, but does not contradict annotations. However, it doesn't add significant behavioral context beyond the endpoint.

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 somewhat verbose and contains redundancy (e.g., 'Return detailed information' and 'Returns a JSON object'), as well as a grammatical issue ('a specific Invoices'). It could be more concise.

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 simple read-only tool with good annotations, the description covers the basics but is somewhat confusing due to the mix of 'Async Job' and 'Invoices.' It does not explain pagination parameters, which are in the schema but not mentioned. Adequate but not complete.

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?

The input schema has 100% coverage with descriptions for all four parameters. The description only repeats the required parameters (uuid, company_id) without adding new meaning, so no extra value 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 states 'Return detailed information about a specified Async Job' but then confuses by saying 'fetch the full details of a specific Invoices,' mixing the async job with invoices. This creates ambiguity about the actual resource being queried.

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 provides basic usage ('Use this to fetch...') but does not specify when not to use this tool or mention alternative tools. Among many sibling show_* tools, no contextual differentiation is provided.

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