list_conan_profiles

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

No annotations are provided, so the description must carry the burden. It states the tool is for inspection and returns a list of profile names, implying no destructive actions. It could explicitly state it is read-only, but given the simplicity, it is adequately transparent.

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 short but slightly repetitive (first sentence restates the title-like phrase, then repeats the purpose). The format is clear with a 'Returns:' section, but it could be more concise by merging the first two sentences.

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 the tool has no parameters and an output schema exists (though not shown), the description provides the essential information: what it does and what it returns. For a simple list operation, it is sufficiently complete.

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?

There are no parameters (0 parameters, 100% schema coverage). The baseline for 0 parameters is 4. The description adds no parameter insight because none exist, which is appropriate.

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 lists Conan profiles. It uses a specific verb-resource combination ('List Conan profiles') and distinguishes itself from sibling tools like 'get_conan_profile' by indicating it returns all available profiles or inspection.

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 explicitly says to use this tool to see which profiles are available for selection or inspection, giving clear guidance on when to use it. However, it does not explicitly mention when not to use it or compare to alternatives like 'get_conan_profile'.

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