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

Annotations provide readOnlyHint=true, and the description adds meaningful behavior beyond that: it is a single-entity synthesis, standalone as opposed to composite, and has associated pricing/plan inclusion. It does not fully describe return shape or rate-limit behavior, but the read-only safety is covered by the annotation.

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 dense but front-loaded with the core point (one provider, standalone score) before the alternative and pricing. The parenthetical dimension list is helpful, though the pricing sentence could arguably live outside the tool description.

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 read-only single-entity getter with one required param and no output schema, the description is complete enough: it states scope, semantics, alternative, and pricing. It stops short of describing the score's format or range, but that is a minor gap 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?

The description clarifies that the operation targets ONE provider, giving meaning to the required slug, while the context parameter already has a thorough schema description explaining it is never used for ranking. The standalone/composite distinction also helps the agent interpret what the score means.

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/explore mode, an explicit resource ('agent-readiness dimensions and standalone score for ONE provider'), and includes a concrete list of dimensions. It also explicitly distinguishes itself from find_agent_readiness, making the scope immediate.

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 an explicit alternative for a different question ('For the same question across the catalog... use find_agent_readiness') and clarifies it is a standalone score rather than a slice of the composite. This tells the agent both when to invoke it and when to pick another tool.

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