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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so safety is covered. The description adds that an empty call returns an overview and that a guide URI exists, but says nothing about what 'diagnose' does or what changes when source/entity are supplied.

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 short and front-loaded, but written as cryptic fragments ('e.g. {}; biomedmcp://guide') rather than complete sentences, so brevity comes at the cost of comprehension.

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?

An output schema exists so return values need not be explained, but for a three-parameter introspection tool with an undocumented enum and an unexplained boolean flag, the description leaves the agent without enough information to invoke it intentionally.

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 0% across three parameters, including a 17-value entity enum with no descriptions. The description never maps 'source', 'entity', or 'diagnose' to behavior ('diagnose' is not mentioned at all), so it fails to compensate for the documentation gap.

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 verb 'Inspect' and objects 'enabled sources, workflows, sections' give a rough sense of a discovery/introspection tool, but 'sections' and 'an advanced operation's exact schema' are undefined and nothing distinguishes it from siblings like query_source or get. An agent can guess it is the introspective entry point but not precisely what it returns.

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 only usage hint is 'e.g. {}', implying a no-argument call yields an overview, plus a pointer to 'biomedmcp://guide'. There is no statement of when to prefer this over query_source, get, or search, and no conditions under which it should not be called.

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