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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so safety is covered. The description adds nothing beyond that: it does not say whether the result is a fixed catalog, whether it costs anything, whether 'target' must be an existing record type, or how errors on invalid targets behave.

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?

It is a single short sentence with no wasted clauses, so it is concise, but that brevity comes at the cost of specificity rather than being achieved through precision. Front-loading is fine; there is simply very little content.

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 discovery tool with no output schema, the description should convey what the returned list looks like (fields? operators? facts names?) and what 'target' accepts. Neither is present, leaving the agent unable to construct a valid call with confidence.

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 0% for the single required 'target' parameter, so the description must carry the meaning. 'One kind of record' is a weak hint at most; it does not say what form the target takes, what values are accepted, or whether it is a record type name, ID, or spec reference.

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 verb 'Lists' and the object 'conditions and facts SpecStream can check' give a rough sense of a discovery/options tool, but the resource is described in domain jargon and 'one kind of record' does not clearly connect to the required 'target' parameter. It is distinguishable from get_spec or create_spec only by inference, not by explicit contrast.

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 statement of when to call this versus siblings such as get_spec, list_your_fields, or create_spec, and no mention of prerequisites (e.g., that it should be called before authoring a spec). Usage is only implied by the word 'options'.

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