Integration

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so 'Read-only' in the description is a redundant restatement that adds no context. Nothing is disclosed about what the integration object contains, whether it can return an unconfigured/empty state, or any auth scoping needs.

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?

It is short and front-loads the endpoint path, but the leading fragment 'Integration.' merely duplicates the title and earns no place. The brevity comes at the cost of substance rather than from disciplined editing.

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 simple read-only tool with no output schema, the description should at least hint at what the Microsoft Teams integration payload represents (connected tenant, sync status, configuration). As written, an agent knows only that it is a GET, leaving a real gap on return semantics.

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?

There is only one optional parameter (response_format) with 100% schema description coverage including allowed enum values and defaults. The description says nothing about it, but the schema fully carries the semantics, so baseline 3 applies.

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 reduces to the resource word 'Integration' plus an HTTP endpoint hint '(GET /microsoft_teams/integration)'. The verb is only inferable from the GET method rather than stated, and the title is a pure restatement. It identifies the resource but does not differentiate this from sibling Microsoft Teams tools such as list_microsoft_teams_users or import_microsoft_teams_user beyond name inference.

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 statement of when to call this versus the many sibling microsoft_teams_* tools, no prerequisites, and no exclusions. The agent must infer from the tool name alone that this retrieves account-level integration configuration rather than user data.

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