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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds no further behavioral traits — no note on caching, freshness, or whether 'release-bound' config can change between calls — so it stays at an adequate-but-minimal 3.

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?

Two sentences, no filler. The content enumeration comes first and the trigger condition is second, so the agent gets payload and timing up front.

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 restated, and both optional parameters are documented in the schema. The description is nearly complete for a low-complexity read tool; only the interaction between factoryType and the returned config is left implicit.

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 100%: chainId's conditional requirement and factoryType's enum/default are fully documented in the schema. The description says nothing about either parameter, so baseline 3 applies.

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?

States a specific verb and resource ('Get the ... factory configuration') and enumerates the contents the caller receives: collaterals with seed/buy minimums, creator lock, duration limits, and fees. This lets an agent separate it from neighbours like problee_list_collateral and problee_get_fees without opening a schema.

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?

Explicitly names the moment to call it: 'Use this before creating markets to know protocol constraints.' That gives clear context, though it offers no exclusions or named alternative for related questions such as fee lookups.

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