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

Annotations already declare readOnlyHint/openWorldHint/destructiveHint, so the safety profile is covered. The description adds meaningful beyond-annotation context: it does not process documents and is normally not billed, plus the underlying GET endpoint. Return shape is not described, but no output schema exists to lean on, making this a modest gap.

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 compact sentences: purpose and allowed values first, then the disambiguating constraint, then the endpoint. Nothing is padded and the key routing information is front-loaded.

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 discovery tool with no output schema, the description is nearly complete: it says what is listed and gives representative model types. Only the exact return format (IDs vs. names, ordering) is unspecified, which is a minor gap given the simple surface.

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?

Zero parameters, so the baseline is 4 under the rubric. The description adds no parameter detail, but there is nothing to document, and the empty schema is fully consistent with the stated behavior.

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 ('List the document capturing models enabled for this project') and enumerates the model types returned. The sentence 'Does not process a document' directly distinguishes it from the capture_* siblings, so an agent can route correctly without opening a schema.

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?

Clearly frames this as a discovery/metadata call with no side effects and no billing, which tells the agent when it is appropriate. It stops short of explicitly naming the capture_* alternatives as the next step, so it is clear context rather than full when/when-not routing.

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