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

Annotations already declare readOnly, idempotent, non-destructive, non-open-world behavior, so the safety profile is covered. The description adds genuinely new context: this is a static lookup that performs no computation on user data, which tells the agent no user context is required. It also conveys the shape of the return (reference tables with known cardinalities) in the absence of an 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 purpose is front-loaded and the constraint sentence is short and load-bearing. The long enumerated list is verbose but every item maps to a real parameter value, so it earns its space rather than padding.

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?

With a single enum parameter, complete annotations, and no output schema, the description supplies everything needed: the full set of valid topics with content hints and the behavioral note that no user data is involved. Nothing an agent needs in order to call this correctly is absent.

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% with a fully documented enum, so the baseline is 3. The description goes beyond the bare enum labels by describing the content of each topic ('the four stages and their exit gates', 'the 10 product types with their risk priors and build rules'), which helps the agent pick the right value.

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+resource ('Return one of the method's reference tables') and enumerates exactly which tables exist, so an agent knows the full retrieval surface. The closing clause 'Static reference, no computation on user data' cleanly separates it from computational siblings like classify_idea, cut_mvp, and validation_plan.

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 phrase 'Static reference, no computation on user data' implicitly tells the agent to use this when the method definition itself is needed rather than when applying the method to a user's idea. No sibling is named explicitly and there is no explicit when-not-to-use statement, so it stops short of a 5.

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