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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds useful context that this reads public, section-scoped pages addressed by a path. It stops short of describing pagination or content shape, but for a simple read that's a minor gap and the output schema covers returns.

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?

Two tight sentences: purpose and value examples come first, then the routing alternatives. Zero filler and front-loaded with the key action.

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-parameter read tool with a 100%-covered schema, full annotations, and an output schema, the description supplies everything an agent needs: what it fetches, how to construct the path, and which sibling to use otherwise.

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%, so baseline is 3, but the description adds meaning by naming example section values (fixtures, results, standings, squad, stats) and explaining that the path comes from copying a tab href. That goes beyond the schema's structural description of the path string.

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 (Fetch) and resource (public LiveScore team page section by path), with concrete section examples (fixtures, results, standings, squad, stats). An agent can distinguish it from the surrounding livescore_* siblings without opening any schema.

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?

Explicitly routes the agent: use livescore_search to find teams, livescore_match for one event, livescore_player for a squad member, livescore_competition for a competition. It also tells the agent how to obtain the required value ('Copy the tab href from the team page').

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