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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally; the description only confirms the content is a normative reference. It does not disclose the shape or size of what comes back (a single guide blob vs. sections), which matters since there is no output schema.

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 with no filler: the first front-loads scope and the enumerated topics, the second gives the actionable instruction. Nothing is repeated and nothing needs trimming.

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 zero-parameter, read-only reference tool with no output schema, the description covers purpose, normative basis, and invocation timing adequately. The only shortfall is not hinting at the return format or length, which an agent may want in order to plan context usage.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The content enumeration still usefully tells the agent what topics the guide addresses, which aids interpretation of the result.

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 (a short normative guide to writing Aranese under the IEA norm) and enumerates its coverage: articles, compulsory contractions, common words, and typical Catalan/Spanish/general-Occitan errors. It implicitly separates itself from processing siblings (corrector, dictionary, translator) by framing itself as a static reference, though it never names those alternatives 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?

'Read it before writing Aranese' gives a concrete trigger condition for invoking the tool. There is no explicit when-not guidance or named alternative for cases where the agent instead wants correction or translation, leaving that routing to inference from sibling names.

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