List private school profiles

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description does add meaningful context about data minimization: it explicitly says credential values, paths, provider identity, and network are excluded, which tells the agent the output is limited to non-sensitive metadata. That is genuine value beyond annotations, though it does not describe return shape or freshness.

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?

It is a single compact sentence with no wasted words, which is good, but it is a fragment that doesn't front-load the core action. The most important information for an agent—that this lists account metadata—is absent rather than leading.

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 no-argument, read-only list tool, annotations and the schema cover most of the burden, and the exclusions add useful scoping. However, the description never says what the tool actually returns (account/profile entries) or how it is distinct from the other list_* tools, leaving a real gap an agent must guess at.

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?

With zero parameters the baseline is 4. There is nothing to document, and the description appropriately spends no space on non-existent inputs.

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 tool is named list_accounts with title 'List private school profiles', but the description never states that it lists accounts or profiles. Instead it enumerates metadata fields ('labels/default/version/auth source availability only'), which reads more like a scoping caveat than a statement of purpose. An agent cannot confidently tell what resource is returned or how it differs from list_users or list_courses.

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?

There is no when-to-use guidance and no mention of alternatives among the many list_* siblings. The only directive is a negative scope ('No credential values, paths, provider identity or network'), which tells the agent what it will NOT get but not when this tool is the right choice.

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