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

With no annotations, the description must carry the full behavioral burden. It discloses that it returns runnable collections and that include=['content'] inlines bodies, which is useful. However, it does not mention pagination, ordering, match semantics, or the context parameter behavior, leaving significant behavioral aspects undocumented.

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?

Three sentences, each adding distinct value: what it finds, filter options, and an alternative tool. Information is front-loaded and there is no fluff. Slightly more could be said about sorting/pagination, but as a concise summary it works.

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?

Given it is a list/search tool with 9 parameters and many sibling find_* tools, the description provides essential filtering info and one alternative, but it lacks guidance on pagination, sort behavior, and the purpose of the context parameter. With no output schema, the agent is left guessing about the return structure. Overall adequate but not complete.

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 coverage is 44%, so the description should compensate for undocumented parameters. It explains q, tags, providers, and include, giving meaningful semantics. But it omits page, sort, limit, match, and context, which are not fully described in the schema either. The description adds some value but does not fully cover the gaps.

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 clearly states the tool finds Postman/Open collections that are runnable request collections, and lists key filters. It distinguishes itself from find_artifacts but does not explicitly differentiate from closely related find_postman, so it is good but not perfectly unambiguous among siblings.

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 an explicit alternative: 'Use find_artifacts for cross-type search.' This provides clear direction on when not to use this tool. However, it does not mention other potential sibling alternatives like find_postman or when to choose this over them, leaving some ambiguity.

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