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

No annotations are provided, so the description must disclose behavior. It only says 'Get sent Outlook emails', which does not mention whether results are limited to metadata, whether authentication is required, pagination, or any other behavioral aspects. The safety of this read operation is implied but not explicitly stated, leaving behavioral transparency largely unaddressed.

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 structurally concise, but it is under-specified. It omits essential information about parameters and scope, making it insufficient rather than efficiently concise. For a tool with parameters and no annotations, this level of brevity is not 'appropriately sized'.

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 tool with two optional parameters that are undocumented, no annotations, and no output schema, the description is grossly incomplete. It does not explain what the parameters do, what the return format is, or any limitations. Sibling tools like get_outlook_inbox and get_sent exist, but without more context, an agent cannot reliably use this tool. It is barely above a minimal stub.

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 defines two parameters (q and limit) with no descriptions, and the tool description does not clarify their meaning or usage. With 0% schema description coverage and no parameter info in the description, the agent is left to guess what q filters and what limit does. The description adds no value beyond the parameter names.

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 'Get sent Outlook emails' clearly identifies the action (get) and resource (sent Outlook emails), which is specific and understandable. It distinguishes from sibling tools like get_outlook_inbox by explicitly referencing the 'sent' folder, though it does not mention alternative tools like get_sent. However, the brevity does not fully disambiguate from get_sent, so it loses a point.

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?

There is no guidance on when to use this tool versus alternatives such as get_sent or get_outlook_inbox. The description only states what the tool does without any context about preferred use cases, exclusions, or prerequisites. With numerous sibling email tools, this lack of guidance makes it harder for an agent to select the right one.

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