get_r_asset_asset_shares_id

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

With no annotations, the description carries the behavioral burden. It conveys a read-only intent via 'Retrieve' and `GET`, and it mentions filters and pagination, which hints at request behavior. However, it does not disclose authentication needs, response shape expectations, or whether the route ID is mandatory despite the schema listing no required parameters.

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 a single sentence that front-loads the resource and endpoint, then maps arguments to their locations. It is compact and free of filler, though the phrase 'any required request headers in headers' is somewhat boilerplate.

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?

The description is adequate for a simple GET-by-ID call and the output schema exists, so return values need no explanation. However, it omits whether the ID is required, how the query filters/pagination are structured, and any auth or error context. Given the low schema coverage, more contextual detail would improve call success.

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 tells the agent that path_params hold route IDs, query holds filters/pagination, and headers hold required headers. This is useful but remains generic; it does not specify actual parameter names, value formats, or which pagination/filter keys are supported.

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 a specific verb and resource ('Retrieve asset share') and explicitly shows the endpoint `GET /r/asset/asset_shares/{id}`. It is clear that this tool fetches a single asset share, though it does not explicitly contrast itself with the sibling collection endpoint `get_r_asset_asset_shares`.

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?

There is no guidance on when to choose this tool over alternatives such as `get_r_asset_asset_shares`, nor any mention of prerequisites or exclusions. The phrase 'Provide route IDs...' is operational instruction, not usage context. An agent must infer the intended single-record use case from the name and endpoint.

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