get_assessment

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It neither states that the operation is read-only nor describes what the 'detail' includes, error behavior, or any side effects. For a getter, the absence of such information is a noticeable gap.

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 concise sentence with no redundant words. The action and primary selector are front-loaded, making it easy to scan and parse.

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 tool with one parameter, no output schema, and no annotations, the description is minimal to the point of leaving significant gaps. It does not indicate what fields are returned, how to handle non-existent slugs, or any related context. While simple, it lacks enough detail for an agent to fully anticipate the outcome.

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 description mentions the parameter ('by slug'), which adds meaning beyond the raw schema (a bare 'string'). However, it does not elaborate on slug format, uniqueness, or expected values. Given schema coverage is 0%, the description partially compensates but stops short of full semantic clarity.

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 ('Get') and resource ('assessment detail') identified by a slug. It clearly distinguishes the tool from siblings like list_assessments, update_assessment, and create_assessment, making its purpose unambiguous.

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 no explicit guidance on when to use this tool versus alternatives. While it implies a single-asset fetch, it does not mention when to prefer it over list_assessments or any exclusion conditions. This leaves the agent to infer usage from the name alone.

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