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

Annotations already declare read-only, idempotent, non-destructive behavior. The description adds useful context about being no-charge and restricted to named official sources, which gives some behavioral detail beyond the schema. However, 'LIMITED' and 'claims' are ambiguous, so the added transparency is modest.

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 very short (two sentences) and avoids unnecessary words. However, its brevity comes at the cost of clarity, making it cryptic rather than efficiently informative. It is concise but not appropriately sized for the needed 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?

Despite having an output schema and rich annotations, the description fails to explain the core detection behavior or the meaning of 'claims'. It leaves the agent uncertain about what constitutes a material change and how the output should be interpreted. For a tool with no parameters, the description should at least clarify the domain logic.

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?

There are zero parameters, so the baseline is 4. The description doesn't add parameter-specific meaning but none is needed; the empty schema with additionalProperties true is the only parameter-related concern, but it doesn't need explanation.

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 essentially restates the tool name via the API identifier 'gb.company.material_change.detect.v1' without explaining what 'material change' means or what the tool actually does. It adds a cryptic constraint about 'claims limited to named official sources' but fails to state the core purpose in plain language, making it barely more than a tautology.

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 mention of when to use this tool versus any of the sibling tools such as verify_uk_company_status or run_uk_company_check. The statement about being 'public no-charge' and 'limited to official sources' implies a cost/scope boundary but provides no situational guidance.

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