exchange_get_exchange_certificate

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only says 'Get' and 'expiry monitoring,' so it implies a read operation but does not disclose whether it returns all certificates, how the optional server parameter affects results, or what response shape/status to expect.

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 concise phrase with no fluff, and the core verb/resource are front-loaded. It earns a high score for efficiency, but it is so brief that it leaves behavioral and parameter details unstated.

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 one-parameter tool with no output schema and no annotations, the description is minimal. It tells the agent what domain the tool covers but not how to use the server parameter, what data comes back, or what makes this distinct from other monitoring tools like exchange_get_server_health.

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 description coverage is 0% and the tool description does not mention the 'server' parameter at all. The property name alone hints at a target server, but without required/optional semantics or effect on the returned certificates, the description does not compensate for the missing schema documentation.

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 uses a specific verb ('Get') and resource ('Exchange certificates') and adds a clear use-case parenthetical ('expiry monitoring'). It distinguishes the tool from its many mailbox/connector/queue siblings by resource, though it doesn't state whether this returns all certificates or a filtered set.

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 given about when to use this tool versus alternatives, and there are dozens of sibling tools. The agent is left to infer that certificate-related monitoring is the intended niche; there are no exclusions or explicit conditions.

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