zernio_list_profiles

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

No annotations exist, so the description must carry the full burden. It correctly indicates a read-only list operation, but does not disclose potential limitations like pagination, rate limits, or permission requirements. Since it is a simple list with no parameters, the description is minimally adequate but could be more specific.

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 concise sentence that immediately conveys the tool's purpose. It is front-loaded with the verb and resource, and the parenthetical adds clarity without waste.

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 that there is no output schema, the description should ideally describe the return value (e.g., an array of profile objects or IDs). It does not, and with many sibling list tools, more context about the scope or listing behavior would be beneficial. However, for a straightforward list without parameters, it is minimally 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, and schema coverage is 100%. The description adds value by explaining what a Zernio profile is, which is not present in the schema. Baseline for 0 params is 4, and this is appropriately applied.

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 verb 'List' and the resource 'all Zernio profiles', with an explanatory parenthetical defining profiles as brand/project containers. This distinguishes it from siblings like zernio_get_zernio_profile (single profile) and zernio_create_zernio_profile (creation).

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 provides no guidance on when to use this tool vs alternatives (e.g., when to list vs get a specific profile). It lacks context about prerequisites, whether it lists profiles for the current user or system-wide, or any other usage hints.

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