list_profiles

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

The description discloses the read-only, non-destructive behavior ('List'), which is adequate for a simple listing tool. However, it does not mention authentication needs, rate limits, or result format (e.g., pagination, fields returned). With no annotations, the description carries full burden and is minimally 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 a single, front-loaded sentence with no wasted words. It directly states the action and target, earning its place with maximum conciseness.

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 no output schema or annotations, the description is minimal. It conveys the primary function but lacks details about return values, potential errors, or behavior under edge conditions. For a simple list tool, it is adequate but not fully 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?

The tool has zero parameters, so the baseline is 4. The description does not need to add parameter semantics, and the schema coverage is 100%. No further value is needed.

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 'List all Weik.io profiles', using a specific verb ('List') and resource ('profiles'). It distinguishes from sibling tools like 'add_profile' (creation) and other configuration tools. However, it could clarify the scope (e.g., user's profiles vs system-wide) and lacks mention of returns.

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?

No guidance is provided on when to use this tool versus alternatives. While the purpose implies usage when a profile list is needed, there is no mention of prerequisites, alternatives, or when not to use it (e.g., for filtering).

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