nexterm_list_script_sources

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that — no note on whether results are filtered by source, whether sources must be synced first, or how entries relate to the source records.

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 short sentence with no waste, which is appropriate in size for a zero-argument list tool. However, the terseness comes at the cost of under-specification rather than efficient communication — one more clause defining "source-backed" would have paid for itself.

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?

Although complexity is low (no params, no nested objects), the definition still leaves the agent unable to predict what comes back or how this differs from the many sibling list tools. With no output schema and no explanation of the domain concept, the description does not carry its share of the burden.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The schema is an empty object with additionalProperties=false, consistent with the description implying no filtering options.

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?

"List source-backed scripts" is essentially a restatement of the tool name (nexterm_list_script_sources) and leaves the key concept — what a "source" is in this domain — undefined. It also does nothing to separate itself from nexterm_list_scripts, nexterm_list_all_scripts, or nexterm_list_snippet_sources, all of which sound like they return similar collections.

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?

There is no indication of when to use this instead of nexterm_list_scripts or nexterm_list_all_scripts, nor any prerequisite or exclusion. The agent must guess which of the several list-* tools returns the right collection.

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