outlook_list_contacts

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

No annotations provided; description mentions cursor pagination but lacks details on read-only nature, rate limits, ordering, or error handling. Adequate for a simple list operation.

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, no redundancy, front-loaded with purpose and guidance. Efficient use of words.

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?

Covers purpose and sibling differentiation but lacks details on return format, limits, or usage in absence of output schema and annotations. Adequate for a straightforward tool.

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 has 0% description coverage, and description only hints at cursor pagination without explaining 'count' or 'cursor' explicitly. Minimal 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?

Clearly states 'List contacts with cursor pagination', specifying verb and resource, and distinguishes from sibling 'outlook_list_contacts_delta' by usage context.

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 contrasts with 'outlook_list_contacts_delta' for one-shot vs polling, but does not mention other related siblings like 'outlook_search_contacts'.

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