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

No annotations are provided, so the description carries the full burden — and it delivers. It discloses default section omission with counts still reported, view/fields switching behavior, relative URL resolution to absolute, and the `next` affordance block behavior and how to disable it. This is rich behavioral disclosure for a tool with zero annotation coverage.

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?

Front-loaded with the main purpose and every clause carries information — default omission, full view, cheap reads, URL resolution, and next-block behavior all earn their place. It is dense and fairly long, but no sentence is filler; it only loses a point for packing many behavioral facts into a wall of prose rather than a tighter structure.

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 5-parameter tool with no output schema and no annotations, the description covers defaults, variants, narrowing paths, output affordances (next), and transformation behavior. It does not depict the actual profile/rating fields, but with no output schema declared that burden lands on the tool's response; the description covers what an agent needs to call it confidently.

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 80% (high), so the baseline is 3. The description adds concrete value beyond the schema with worked examples like fields=["score"] returns just the rating and fields=["common"] for a section, going beyond the schema's generic 'Return exactly these top-level keys'. That pushes it above baseline.

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 ('Full detail for one provider') with resource, scope, and content ('profile, rating, and the APIs it publishes'). The 'one provider' phrasing clearly separates it from sibling search tools like find_providers and from narrower detail tools like get_provider_rating and get_provider_artifacts.

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?

Gives clear context on parameter-driven usage ('Narrow for cheap reads', 'pass view=full for the whole document') that implies when each mode is appropriate. However, it never names sibling alternatives or states explicit exclusions (e.g., when to prefer get_provider_rating or get_api instead), so it stops short of the strongest guidance.

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