konsulto_list_my_audits

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

No annotations provided, so description carries full burden. It states the scope (user's team members) and filtering capability. However, does not disclose pagination, ordering, or whether it returns full audit details or just IDs. Basic but lacks deeper behavioral insights.

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 states function, second states usage and filter. No unnecessary words, front-loaded with key action.

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 and simple list tool, description is adequate for its purpose. It explains how to find audit ID, which aligns with sibling tools. Could mention limit parameter or return data format, but not essential.

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 50% (status described, limit not). Description repeats status filter from schema but adds nothing for limit. Baseline 3 reduced because description fails to compensate for missing limit description.

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 lists audits where the user is a team member, with a specific purpose: to find the audit ID to work in. This distinguishes it from siblings like konsulto_search_templates or konsulto_list_scope.

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 states usage context: find audit ID for subsequent work. Implies it is a prerequisite for tools requiring an audit ID. No explicit when-not-to-use or alternatives, but context is clear.

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