list_checker_options

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

No annotations provided, so description carries the burden. It discloses that this is a read operation ('Get all') and clarifies the semantic meaning of profileId (lens vs container). Does not discuss error states or pagination, but for a simple list tool this is sufficient. Score 4 for good behavioral insight despite missing annotations.

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, no filler. Purpose stated first, then a crucial usage note. Highly efficient and well-structured.

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?

No output schema, so description doesn't explain return format. However, for a list tool with 3 parameters and clear purpose, the description is largely complete. Lacks mention of pagination or error handling, but that is minor given the tool's simplicity.

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%, so baseline is 3. Description adds value for profileId by explaining it selects a lens, not a container. For staged and checkerId, it provides no additional context beyond schema. The added critical nuance justifies a 4.

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?

Clearly states 'Get all the checker options related to a profile and checker.' Verb 'Get' and resource 'checker options' are specific. Distinguishes from sibling tools like list_checkers and create_checker_option. Clarifies that profileId selects a lens, not a container, adding nuance.

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?

Explicitly advises: if profile not specified, call get_preferred_profile (or get_preferences) and use preferredProfileId, and warns not to assume profile 1. This tells the agent when and how to use the tool, including a prerequisite step.

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