m365_send_email

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

With no annotations and an input schema with zero properties, the description fails to explain that the tool apparently sends an email without any parameters. It does not disclose how the email content is determined or if there are side effects. The description contradicts the expectation that sending an email requires inputs.

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, which is concise but underspecified. It fails to provide enough information for an agent to use the tool correctly. Conciseness should not come at the expense of clarity.

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 lack of output schema and input parameters, the description should explain what constitutes an email (e.g., uses a pre-set draft or default template). It does not, making the tool's behavior completely opaque. The agent cannot determine how to use it effectively.

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 schema has zero parameters and 100% coverage, but the description does not clarify how the email is sent without input. It adds no value to explain the meaning or use of the nonexistent parameters, leaving the agent confused about how to invoke the tool.

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 verb 'Send' and resource 'email' with the source 'your Microsoft 365 account'. It indicates the core purpose. However, it does not differentiate from sibling tools like 'send_email' or 'create_draft', which may have overlapping functionality.

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. For example, there is no mention of prerequisites like having a connected Microsoft 365 account or that a draft may be needed. The description offers no usage context.

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