list_profiles

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

Description discloses sorting (by user count desc) and that unassigned profiles are included. However, no annotations exist, and the description does not mention side effects, permissions, or error conditions. Adequate but incomplete.

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?

Three short sentences, each adding value (output fields, ordering, edge case). No redundant or missing words; front-loaded with key information.

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 2 parameters, output schema exists, and no nested objects, description covers input, output, ordering, and an edge case (unassigned profiles). Minor gap: error handling or required snapshot validity not addressed.

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 0%, but description adds context: output includes 'user count' which relates to include_user_counts param. Snapshot_id is implied but not explained. Partial compensation for missing schema descriptions.

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 verb ('list') and resource ('Profiles in a snapshot') with specific output fields (name, license, user count, perm cardinality, ModifyAllData). Distinguishes from siblings like snapshot_org or permission_diff by focusing on profile listing.

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 explicit guidance on when to use this tool versus alternatives (e.g., describe_object, permission_diff). Context implies use for profile overview but lacks when-not or sibling comparisons.

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