get_competitor_comparison

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

No annotations are supplied, so the description carries the full burden, but "Retrieve" makes the read-only nature self-evident and "verified, source-cited" usefully signals that results come with provenance. It does not disclose response format, pagination, or how the matrices are structured, and there is no output schema to compensate.

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?

One front-loaded sentence with the verb, resource, and scope stated first. The long parenthetical roster of twenty competitors is verbose but does real work by telling the agent exactly which comparisons exist, so it earns its space despite the length.

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 simple read-only lookup with one optional parameter and no output schema, the description covers what is returned and the full coverage scope of competitors. The only gap is that it doesn't characterize the shape of a returned matrix or benchmark, which an agent might want when summarizing results.

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 100% and the single slug parameter is well documented in the schema, including example values and the "omit to list all 25" behavior, so the baseline of 3 applies. The description adds no parameter-level detail beyond what the schema already says.

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 ("Retrieve") and a specific resource ("verified, source-cited side-by-side comparison matrices and best-of benchmarks") scoped to Smarter.Poker versus named competitors. An agent can tell this apart from siblings like get_platform_feature_specs or get_research_report, though the description never names an alternative explicitly.

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?

Usage is only implied by the resource type: an agent can infer it should call this when a user asks how Smarter.Poker stacks up against a named competitor. There is no explicit when-to-use, when-not-to-use, or routing to sibling tools such as get_platform_feature_specs for raw feature data.

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