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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description goes further by disclosing a hard result cap (max 200) and a truncation signal (sources_truncated: true if cut), which is real behavioral context an agent needs to detect incomplete results.

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 dense sentence with no wasted words; the resource and the return fields lead, and the limit/truncation caveat is packed into a trailing parenthetical where it belongs. Every clause carries information.

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?

With no output schema, the description usefully enumerates the returned provenance fields and the truncation flag, and the 2-parameter surface is small. What is missing is minor: no ordering guarantee and no guidance on what to do when sources_truncated is true (e.g., no pagination path).

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 50%: entity_id is documented ('Entity UUID') but entity_type has no schema description. The description partially compensates by specifying the entity is a club, matching the single enum value, but adds no syntax or format guidance beyond that. Baseline 3 is appropriate.

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?

'List provenance ... for a club' states a specific verb and resource and enumerates the returned fields (source URL, publisher, trust level, field, retrieved_at), which is far more specific than the bare name. It does not explicitly differentiate from get_club/search_clubs, but the provenance-listing scope is plainly distinct from those.

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 phrase 'for a club' implies the usage context (fetch sourcing/provenance for a known club entity), but there is no explicit when-to-use vs when-not, no statement of prerequisites, and no pointer to an alternative for broader searches. Usage is inferable but not stated.

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