jms_get_asset

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It mentions 'observed perms endpoint' but does not clarify whether this is read-only, what response format to expect, or any error/edge-case behavior. This is minimal disclosure for a tool with no annotation support.

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 short sentence, but the phrase 'through the observed perms endpoint' is vague and arguably unnecessary. It does not add actionable value and could confuse the agent, so while concise in length, it is not optimally structured for clarity.

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 one-parameter fetch tool with an output schema, the description is minimally adequate. However, it lacks guidance on how asset_id relates to sibling tools and gives no behavioral context. The odd 'observed perms endpoint' phrasing further detracts from completeness, making this a borderline viable but not rich description.

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 schema has 0% description coverage for the sole parameter asset_id, and the description does not explain it or add meaning beyond the parameter name. While 'asset_id' is somewhat self-explanatory, the description fails to mention that this ID should be obtained from jms_list_assets or similar, leaving a semantic gap.

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 'Fetch one asset detail', using a specific verb and resource. It distinguishes itself from sibling tools like jms_list_assets (list all) and jms_get_asset_access (access details). The phrase 'through the observed perms endpoint' is odd but does not obscure the core purpose.

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 implies usage for fetching a single asset by ID, but it does not explicitly state when to use this versus alternatives like jms_list_assets or jms_get_asset_access. No explicit exclusions or alternative tool mentions are provided, leaving usage guidance mostly implicit.

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