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 disclosing behavior, side effects, and safety. It discloses nothing beyond the tool's name and catalog equivalence, so the agent cannot know if this is read-only, mutating, long-running, or permission-sensitive.

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 definition is under-specified rather than concisely informative. The phrase 'MCP-Agents tool run_credit_screen' is redundant, and the URL reference consumes space that should have been used to describe the tool's function. There is no front-loaded purpose.

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 domain-specific credit tool among roughly 70 siblings, with no output schema and no annotations, the description must explain what the tool does, what inputs it needs, and what it returns; it does none of this. The catalog URL is not actionable for tool selection or invocation.

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 declared parameters and 100% schema coverage, the description has little parameter documentation burden, so the baseline is 4. The only caveat is additionalProperties:true, which the description leaves unexplained, but no named parameters are missing.

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 never states a verb, resource, or function. 'MCP-Agents tool run_credit_screen' merely restates the tool name, and 'Same name as the live catalog...' only references an external URL. It is a tautological definition that does not distinguish this from siblings like run_deal_screening or run_risk_discovery.

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 guidance on when to use this tool versus any alternative. The description includes no conditions, prerequisites, or exclusions. An agent has no basis for deciding whether run_credit_screen is the appropriate tool.

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