list_contact_profiles

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so behavior is safe. The description adds that contact profiles store user data across sessions, but doesn't disclose pagination behavior, permission requirements, or return format beyond the schema.

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 concise sentences. First sentence states the action, second adds useful context about contact profiles. No redundant 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?

For a list operation with no output schema, the description adequately explains what contact profiles are but does not describe pagination behavior, default ordering, or what fields are returned in the list. However, the skip/limit parameters imply pagination, and the read-only annotations cover safety.

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 covers 100% of parameters with descriptions, so the tool description doesn't need to repeat them. It provides useful context about data stored in profiles (name, preferences, conversation history) but doesn't explain how parameters like filter or projectId relate to this data.

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 tool lists contact profiles and explains what contact profiles are. It differentiates from sibling tools like get_contact_profile (single profile) and export_contact_profile by using 'lists', though it doesn't explicitly mention alternatives.

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 on when to use this tool versus related tools like get_contact_profile, create_contact_profile, or export_contact_profile. The description lacks context on prerequisites or typical use cases.

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