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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so safety is covered. The description adds useful behavioral context: the omission of the parameter returns the full subject-area list, and passing one yields its sections and leading cases. It does not discuss result size or pagination, but the output schema carries the return shape.

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 packed sentences, front-loaded with the use case, then the calling modes, then the exclusion. Every sentence earns its place with no redundancy.

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-optional-parameter browse tool with full annotation coverage and an output schema, this is complete: intent, calling modes, exclusion, and a pointer to the alternative tool are all present.

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% for the single optional parameter, so the baseline is 3, but the description goes beyond the schema by explaining the semantic difference between omitting topic (list all subject areas) and providing one (get its sections and leading cases). That is meaning the schema alone does not convey.

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: an overview of an area of HOA law, with concrete examples (board meetings, elections, assessments, records). It is immediately distinguishable from search-based siblings by naming the browsing/overview intent.

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?

Gives explicit when-to-use (user wants an overview or asks what the source covers) and when-not (do not use to answer a specific legal question; use search). It even explains the two calling modes: omit topic to list all areas, pass one to drill into sections and leading cases.

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