datto_edr_api_models

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description's main added value is disclosing the data source (/explorer/swagger.json) and the two behavioral modes (omit = enumerate all; pass = expand one model). It does not mention response size or cost of enumerating all models, a minor gap.

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?

Two tight sentences with no filler; the core action and its data source come first, and the purpose statement follows immediately. Every clause carries information.

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-optional-parameter, read-only discovery tool with no output schema, the description covers what the tool returns in both modes (model list vs. paths and properties) and why an agent would call it. Only the shape/size of the returned model listing is left implicit.

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 coverage is 100% and the schema already documents the model parameter with an example. The description nonetheless reinforces the semantic branch: omit the parameter to list all models, pass it to get paths/properties for one. That adds slight meaning beyond the schema, above the baseline 3.

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?

States a specific verb and resource ('List the API models this Datto EDR instance exposes') plus the two operating modes (list-all vs. single-model detail). This clearly separates it from every sibling, which are concrete resource endpoints (agents_list, alerts_list, etc.), since this one is a discovery/meta tool.

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?

Explicitly names the when-to-use case: 'find filterable field names before building a "where" filter.' It also clarifies mode selection via the optional model argument. It does not name an alternative tool (e.g., datto_edr_raw_request) or state when not to use it, so it falls short of a full 5.

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