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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds meaningful behavioral context by disclosing that every result point carries a source URL and that it returns version notes and implementation partners, which goes beyond the annotation metadata.

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 dense sentence that front-loads the purpose and includes a useful examples sentence. It is not overly verbose and every clause contributes to understanding the tool's scope, though a slight structural split could improve skimmability.

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?

With an output schema present and annotations covering safety, the description is largely complete for a read-only assessment tool. It explains inputs, output composition, and source attribution; minor ambiguity around 'what to settle first' is acceptable given the output schema likely details the returned structure.

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 100%, so the baseline is 3. The description adds value beyond the schema by showing combined ERP+version example inputs like 'Dynamics GP 2018' and 'NAV 2009 R2', which clarifies expected formatting for the erp and version parameters beyond the schema's separate examples.

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 opens with a specific verb and resource: for an ERP (and optionally version/platform), it returns integration fit details. It lists concrete outputs (integrates with Sana/BigCommerce/DynamicWeb/Wardenclyffe, version notes, priorities, guides, partners, source URLs), which clearly distinguishes it from sibling tools like get_erp_partner or search_site.

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?

The description gives clear context about when to use the tool (when assessing ERP fit with an e-commerce platform) and even provides example inputs. It does not explicitly name alternatives or state when not to use it, but the scope is clear enough for an agent to route correctly.

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