get_now_assist_skill

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

Annotations already declare readOnlyHint=true, so the agent knows this is a safe read operation. The description adds the NOW_ASSIST_ENABLED requirement, which is valuable context not captured in annotations. It does not describe error behavior or response format, but given the annotation coverage, a 3 is appropriate.

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 that conveys the action, resource, retrieval key, and a prerequisite. There is no extraneous information or redundancy.

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 getter with one well-documented parameter, read-only annotation, and a clear prerequisite, the description is complete. The term 'definition' adequately indicates the return content, and no output schema is expected, so no additional return-value documentation is needed.

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 fully documents the sole parameter 'sys_id' with a clear description ('System ID of the skill'). The tool description merely repeats 'by sys_id' without adding further semantic detail. With 100% schema coverage, a baseline score of 3 is warranted.

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 specifies a clear action ('Get'), a defined resource ('Now Assist skill definition'), and a precise retrieval criterion ('by sys_id'). It clearly distinguishes this from list_now_assist_skills, which would retrieve multiple skills, and from create/test sibling tools.

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 the correct use case: fetch a specific skill when its sys_id is known. It also mentions the NOW_ASSIST_ENABLED prerequisite, giving important context. However, it does not explicitly contrast with list_now_assist_skills or state when not to use it, so it falls short of a 5.

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