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

With no annotations, the description carries the behavioral burden and does well: it specifies accepted input formats and describes the return shape (one line per property, total £65/property fee, earliest deadline, every FAIL/WARN). It still omits whether the operation is strictly read-only, permission requirements, and error behavior.

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?

Three tightly written sentences, front-loaded with purpose, then input formats, then return summary. Every sentence adds operational value with no filler.

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?

Given there is no output schema or annotations, the description provides enough to call the tool correctly: input formats, required keys, and high-level return values. The exact structure of each per-property line and error handling remain unspecified.

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 the baseline would be 3. The description adds meaningful detail for the portfolio parameter by listing the expected CSV header keys and JSON object shape, though it does not mention the today override parameter.

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 and resource (check English rental properties) and explicitly scopes it to batch operation ('many at once'). This distinguishes it from the single-property sibling check_property without needing to name it.

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 batch scope ('many ... at once') gives clear context for when this tool is appropriate versus a single-property check. It does not explicitly say when not to use it or name the alternative, so it stops short of full guidance.

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

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

With no annotations provided, the description carries the full burden and does well by disclosing the returned checks: registration window, deadline, gas/EICR/EPC validity, fee, upload checklist, and penalties. It implies a read-only check through 'Returns' and 'check', but does not explicitly state side-effect behavior, authentication needs, or error handling.

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 definition is front-loaded and dense: the purpose appears in the opening question and the return contents are summarized efficiently in the second sentence. There is no filler, though the question phrasing is slightly less direct than a declarative purpose statement.

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?

There is no output schema, so the description appropriately enumerates the key returned results. Combined with full parameter descriptions, an agent has enough to invoke the tool correctly, though the description could do more to explain output structure or when to prefer sibling tools.

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 100%, so every parameter is already well documented in the input schema. The description mentions the relevant domains (EPC, gas, EICR, fee, region) but adds no syntax, format, or conditional guidance beyond what the schema provides.

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 clearly identifies a readiness-checking tool for English rental properties and enumerates what it returns, including registration windows, document validity, fees, and penalties. It is specific about the resource and evaluation, but it does not explicitly distinguish itself from sibling tools such as check_portfolio or registration_pack.

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 question format implies that the tool checks readiness, but there is no explicit guidance on when to use it versus alternatives. No siblings are mentioned, and there are no conditions, prerequisites, or exclusions stated.

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

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

With no annotations, the description carries the full burden, and it does disclose meaningful behavior: the output is text the caller must save themselves (the tool does not write a file), events are all-day, and reminders are attached. It does not cover date-format expectations or how missing inputs (e.g. no_gas, region) are handled.

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 sentences, zero waste; the artifact and its contents are front-loaded and the follow-up action comes second. Nothing is padded or repeated.

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 10-parameter tool with no required params, no annotations and no output schema, the description should clarify when to use the single-property path versus the portfolio field and what date formats are accepted. It explains the produced artifact well but leaves the agent guessing about input conventions.

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 only 30% across 10 parameters, so the description needed to compensate. It gives conceptual framing (registration window/deadline, per-certificate expiries, portfolio vs single property) but leaves the date format for epc/gas/eicr/eicr_due, the meaning of region and postcode, and the derivation of the registration window entirely unexplained.

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 verb and artifact ('Build an iCalendar (.ics) file') plus the exact contents (registration window, deadline, gas/EICR/EPC expiries as all-day events with reminders). It is clearly distinguishable from registration_pack, check_property and check_portfolio, though it never names those siblings explicitly to route the agent.

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 implied through the post-generation instruction ('Save the returned text as rentready.ics and import it into Google, Apple or Outlook calendar'), which tells the agent what to do after calling but not when to pick this tool over the sibling checks. No exclusions or prerequisites are given.

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

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

With no annotations, the description does real work: it discloses the return format ('markdown checklist'), the pre-fill logic from the portfolio, the GATHER marking for unknown fields, and that certificates needing renewal are flagged before upload. It does not explicitly state that nothing is uploaded or mutated, but the 'prepare ... before upload' framing makes the non-destructive nature reasonably apparent.

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 purpose and output shape are front-loaded in the first sentence, with the column inventory trailing at the end where it is easy to skip. The column list is dense but functional rather than filler.

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 generation tool with no output schema and no annotations, the description covers purpose, inputs, pre-fill behavior, unknown-field handling, and return format. Remaining gaps (no explicit statement of side effects or handling of malformed portfolio data) are minor.

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 the baseline is 3, but the description adds genuine meaning for the `portfolio` input by listing the optional columns (bedrooms, dwelling_type, ownership, let, occupants, etc.) that the schema only calls 'CSV text or JSON list of properties'. It says nothing extra about `today` or `organisation` beyond the schema text.

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?

Uses a specific verb ('Prepare the registration pack') tied to a named external service, and enumerates exactly what the output contains (service questions, pre-fills, GATHER markers, certificate scan list). This is clearly a checklist-generation tool and is readily distinguished from the check_* and make_calendar siblings.

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 context of use is implied ('for England's Register your rental property service'), but there is no explicit statement of when to call this versus check_portfolio or check_property, nor any prerequisites or exclusions. Usage must be inferred from the purpose sentence.

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