m365_get_contact

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

The description indicates a read operation (Get full details) with no destructive side effects. However, without annotations, it fails to disclose authentication requirements, rate limits, or the exact scope of 'full details'. It is minimally transparent but not misleading.

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 sentence that front-loads the verb and resource. It contains no redundant words and is easy to parse.

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 the empty input schema, lack of output schema, and no annotations, the description is inadequate. It does not explain how to provide the contact ID, what 'full details' means, or how this differs from related tools like m365_list_contacts.

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?

The input schema has no properties, so the description's mention of 'by ID' is contradictory. With schema coverage at 100% (no parameters), the description adds no value and actually misleads by implying a parameter that does not exist.

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 action (Get), resource (full details of a specific Microsoft 365 contact), and method (by ID). It distinguishes from sibling tools like list_contacts and search_contacts which return lists or search results.

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 is provided on when to use this tool versus alternatives. It mentions 'by ID' but does not explain how to obtain the ID or when to prefer this over list or search tools.

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