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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses a cost of 2 credits, but does not explain return format, authentication needs, rate limits, truncation behavior for maxChars, or what happens when an invalid URL is supplied.

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 a single compact sentence plus a cost note, with the resource and scope front-loaded. It is efficient, though the parenthetical cost feels slightly detached from the main usage 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 simple read-style tool with no output schema, the description covers the core purpose and cost, but leaves gaps around return format, section behavior, and maxChars truncation. It is minimum viable rather than fully complete.

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 all three parameters are already documented in the schema. The description adds only mild meaning by indicating that the section parameter retrieves one section, while maxChars and URL format expectations are not elaborated beyond the schema.

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 states a specific resource and operation: retrieving the text of an Act, instrument, or one section from a legislation.gov.uk URL. It clearly distinguishes the tool from search-oriented siblings by requiring a URL, though it does not name legislation_search 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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative is named. The URL-based phrasing implies this is a follow-up to a search tool, but the agent must infer that relationship.

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