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

With no annotations, the description carries the burden of behavioral disclosure. It does clarify that the result is a standalone score rather than a composite slice and that it covers one provider, which is useful, but it does not disclose output shape, side effects, or any read-only guarantees.

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 description is tightly packed into three purposeful sentences: what the tool does, what its score is not, and which sibling to use for the catalog-level question. Every sentence adds decision-relevant information and the core scope is front-loaded.

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 single-provider lookup with two parameters and no output schema, the description gives the key return concept, the dimension list, and a routing pointer to the alternative. It is not fully exhaustive about return formatting or edge cases, but it is complete enough for the tool's apparent simplicity.

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 only 50%: the slug parameter has no schema description. The tool description partially compensates by implying slug identifies ONE provider, and the context parameter is already well described in the schema, but no concrete format or example is given for slug.

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 names a specific verb and resource: getting agent-readiness dimensions and a standalone score for ONE provider. It enumerates concrete dimensions and explicitly contrasts itself with find_agent_readiness, so a model can distinguish this tool from its catalog-level sibling.

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 states both when to use this tool (single provider, standalone score) and when to use the alternative (across the catalog, diffusion questions) by naming find_agent_readiness. It gives an explicit routing rule rather than leaving usage to inference.

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