get_endpoint_catalog

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 covered. The description adds valuable context beyond that: it discloses that app-only TripIt browser flow and websocket protocol metadata are included, and that core flight edits are live-tested with coverage documented in docs/testing.md. That reliability caveat is genuine behavioral information, though it does not describe output shape or catalog size.

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?

The definition is three sentences and front-loads the core purpose before adding scope and testing notes. Each sentence contributes something, though the docs/testing.md pointer is somewhat tangential and could be trimmed without losing agent-critical information.

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?

An output schema exists, so the description need not explain return values. For a zero-parameter discovery tool, the description covers what content the catalog includes and notes coverage limitations, which is sufficient to call it correctly. It could be stronger by clarifying its role relative to get_schema, but the essential context is 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?

The tool takes zero parameters, and the input schema is empty with 100% description coverage, so there is nothing for the description to compensate for. Baseline 4 is appropriate for a parameterless definition.

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 clear verb and resource: 'List every supported HTTP operation, request/response schema and read/write classification.' It also names specific content areas (TripIt browser flow, websocket metadata), so an agent knows this is a catalog/discovery endpoint. However, it never distinguishes itself from the sibling get_schema, which likely overlaps, so it falls short of a 5.

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 explicit when-to-use guidance, no mention of prerequisites, and no comparison to alternatives such as get_schema. The opening 'List every supported...' implies discovery usage, but nothing tells the agent when this catalog is the right choice versus other schema/introspection tools. This matches the 'no guidance' severity level.

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