notory_get_asset

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

No annotations are provided, so the description carries the burden. It discloses the HTTP method (GET), implying a read-only operation, and the endpoint structure. While it doesn't mention errors or auth, the simple read nature makes this sufficient.

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, self-contained sentence that includes the REST endpoint pattern. It is concise and front-loaded with the core action, with no wasted words.

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 single-parameter get tool with no output schema, the description is largely complete. It explains what it retrieves and how. It lacks explicit return-value details, but the implication is clear, and there are no complex behaviors to disclose.

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 already covers the single parameter with a description ('The asset id'), and the schema description coverage is 100%. The description adds no extra meaning beyond echoing 'by its id', so the baseline of 3 is appropriate.

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 exact action: 'Fetch a single asset by its id'. It identifies the specific resource (asset) and the operation (fetch by id), which distinguishes it from siblings like notory_list_assets.

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 intended use is clear: fetch one asset when you know its asset_id. It doesn't explicitly name alternatives or exclusions, but the REST endpoint pattern and 'single asset' wording imply the correct context relative to listing tools.

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