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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It says nothing about side effects, read-only guarantees, permissions, or response behavior; the 'get' prefix weakly implies retrieval but is never stated.

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 very short, but its brevity comes from omission rather than efficiency. The first sentence is redundant with the tool name, and the second sentence only points to a URL without explaining anything about the tool's behavior.

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 annotations, no output schema, an opaque name, and a free-form input schema, the description is far too incomplete for an agent to select or invoke the tool correctly. The external URL is not a substitute for in-description context.

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?

Although there are zero named parameters, the input schema is an open object with additionalProperties:true, leaving the expected input format entirely undefined. The description adds no information about what keys, identifiers, or query arguments the tool consumes.

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 merely restates the tool name ('MCP-Agents tool get_attributed_fact') and adds an external URL reference. It does not define what an 'attributed fact' is, what the tool does, or what resource it acts on, so an agent cannot infer purpose.

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 no guidance on when to use this tool versus the many sibling tools. The external catalog URL hints at an external reference but does not provide selection criteria or alternative routing in the description itself.

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