list_profiles

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

Discloses side effects: read-only, no external HTTP calls, deterministic given backend state. Since no annotations exist, the description fully covers behavioral expectations, matching the ideal for transparency.

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: first explains output, second covers side effects and usage. Front-loaded, every sentence adds value, no 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?

Despite lack of output schema and annotations, the description is fully complete: it specifies return type, side effects, and integration with sibling tools. No gaps.

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?

Tool has zero parameters, so schema coverage is 100% trivially. Baseline for 0 parameters is 4. Description adds no param info, which is fine since there are none.

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 returns all distribution profile names from the YAML backend. It uses specific verb 'return' and resource, and distinguishes from siblings by positioning it as a prerequisite for publish, schedule, and list_subreddits.

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 instructs to use list_profiles before calling publish, schedule, or list_subreddits, and to pass the chosen profile_name. Provides clear context of when and why to use this tool relative to siblings.

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