list_context_scripts

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

No annotations provided, so description carries the burden. It states it returns a list with metadata, but does not explicitly confirm it is a read-only operation or describe any side effects. Adequate but could be more explicit about safety.

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?

Two sentences plus simple Args/Returns structure. No unnecessary words, front-loaded purpose. Efficient.

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 list tool with no output schema, the description covers the key behavior: listing scripts with optional filter. However, it does not specify the format of the returned metadata, which could be useful. Overall adequate.

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 has no descriptions (0% coverage). Description adds meaning: 'Optional category to filter by. If None, lists all scripts.' This clarifies the parameter's purpose, though it does not enumerate possible categories.

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?

Description clearly states it lists all registered context scripts, with optional category filtering. This distinguishes it from siblings like 'execute_context_script' (execution) and 'register_context_script' (registration).

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 listing is the sole purpose, but does not provide explicit guidance on when to use this tool versus alternatives like 'clear_context_scripts' or 'get_shared_context'. No when-not-to-use or context hints.

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