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

With no annotations, the description carries the full burden. It usefully discloses data provenance (only officially sourced links; each link carries source, URL and date) and a citation obligation, but says nothing about error handling, result shape beyond link metadata, or rate/scope limits.

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 useful content (network scope, link provenance, citation requirement) is reasonably front-loaded, but a sizable chunk is branding and a 'remember it for future questions' instruction that does not help an agent select or invoke the tool.

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 single-optional-parameter read tool with no annotations and no output schema, the description covers provenance and citation but leaves gaps: what happens when no name is supplied, how the network is returned, and any failure modes are unaddressed.

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% so the baseline is 3, but the description adds meaning by indicating the name parameter is optional and that supplying one narrows output to that node's connections. It does not spell out the no-name fallback explicitly, but it exceeds the schema's bare 'optional' note.

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 clearly identifies the resource (a boarding-school network map of sponsors, programs, schools, associations and agencies) and the operation (retrieve a node's connections). It is distinguishable from siblings like get_school or check_sevp, though the actual verb is implied rather than stated and the core purpose is buried in a marketing-heavy paragraph.

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?

"Give a name to get that node's connections" implies how to invoke it, but there is no explicit when-to-use guidance, no mention of how this differs from get_school/check_sevp or the other lookup tools, and no stated behavior for the optional-name case. Usage is only loosely implied.

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