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

Annotations already cover read-only, idempotent, non-destructive and closed-world behavior, so the bar is lower, yet the description adds genuinely non-structured context: the data is provider-declared and should not be read as a skill or performance endorsement. It omits pagination behavior even though a cursor parameter exists.

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 short sentences with zero filler, the substantive content front-loaded and the trust caveat immediately following. Nothing needs trimming.

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 described, and the data-provenance caveat is a real addition. But for a five-parameter browse tool with zero schema coverage, the missing filter and pagination guidance leaves the definition under-specified for correct 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?

Schema description coverage is 0% across five parameters, so the description carries the full burden and largely fails: limit, query, cursor, industry and geography are never mentioned or explained. The listed concepts (markets, capabilities) describe return content rather than parameter meaning, giving at best an indirect hint.

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 concrete verb ('Read') and enumerates the resource content (capabilities, portfolio URLs, markets, capacity), which matches the title's 'published provider profiles'. It does not, however, differentiate itself from siblings such as browse_owner_demands or search_businesses.

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 statement of when to choose this tool over alternatives like search_businesses or match_demand_providers, nor any prerequisite or exclusion. The browsing intent is only implied by the name and the word 'Read'.

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