get_constants

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

Given no annotations, the description adequately explains behavior: default returns categories/count, category filters, name overrides category. It lacks mention of error handling for invalid inputs but covers core mechanics.

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 concise with a clear summary followed by usage scenarios and structured Arg section. Every sentence adds value without 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 two-parameter tool with no output schema, the description covers all scenarios: no args, category, name, and precedence. It provides complete guidance for an AI agent to use correctly.

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?

With 0% schema coverage, the description fully compensates by explaining both parameters: category as a filter, name as exact lookup with precedence over category. This adds essential meaning beyond the schema's bare types.

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 clearly states the tool returns LSL constants with optional filtering by category or name. It distinctly separates from siblings like 'check_code' and 'get_pitfalls' by specifying the exact resource and operation.

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?

Explicit instructions are given: call with no arguments to see categories, use category for browsing, use name for direct lookup with precedence. This clarifies when to use each parameter and contrasts with sibling tools.

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