list_now_assist_skills

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety and variability. The description adds the 'requires NOW_ASSIST_ENABLED' prerequisite, which is useful context beyond annotations. No further behavioral traits (e.g., pagination, ordering) are disclosed.

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?

A single sentence with no superfluous words. The key information (action, resource, prerequisite) is front-loaded. Perfectly concise.

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?

Given that the tool is a simple list operation with readOnlyHint and openWorldHint, the description adequately covers the purpose and a key prerequisite. However, it could mention the default limit or that it returns definitions, and it doesn't address the output format since no output schema is provided. Overall, sufficient for a straightforward list tool.

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 coverage is 100% with descriptions for all three parameters (limit, query, active). The description does not add any additional parameter meaning beyond what the schema already provides, so the baseline score of 3 applies.

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 explicitly states the action 'List' and the resource 'Now Assist skill definitions'. The prerequisite 'requires NOW_ASSIST_ENABLED' adds specificity. It distinguishes from sibling 'get_now_assist_skill' which retrieves a single skill.

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 includes a clear prerequisite (NOW_ASSIST_ENABLED), which guides when the tool can be used. However, it does not explicitly mention when to use this tool over alternatives like 'get_now_assist_skill' or other list tools, though the name implies listing multiple definitions.

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