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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, so the safety profile is covered. The description still adds real context: the mutation boundary (changes happen at the source, not here) and the exact facts returned per source — current address, last change, last check-in, associated records.

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?

Three sentences, front-loaded with what the resource is, then use cases, then the read-only boundary. Slightly dense with parenthetical and comma-heavy clauses, but no sentence is filler.

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 no output schema and a single trivially documented parameter, the description supplies everything an agent needs: what each item contains, ordering, and the fact that this tool cannot change addresses. Nothing material is left to inference.

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 and the schema documents it fully at 100% coverage ('leave it out when the token reaches only one'). The description adds nothing about organization_id, so the baseline of 3 applies — the schema does all the work.

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 — dynamic IP sources, defined parenthetically as connections whose address changes — plus ordering (by label) and payload (tags, DNS records, firewalls kept up to date). An agent can distinguish this from list_dns_records or list_dns_zones without opening any schema.

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?

Frames the tool with two concrete questions it answers ('did my office address change?', 'is my dynamic DNS still updating?') and adds a clear negative boundary: an address is changed by the source itself, never through this server. It does not name a sibling alternative explicitly, so it falls short of a 5.

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