spot_api_get

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

The readOnlyHint annotation already declares the safety profile, and the description mainly reinforces it with 'Only GET is supported; this server is read-only.' It adds a useful docs URL and example path, but says nothing about auth requirements, rate limits, error behavior, or what the response contains beyond the raw API response.

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?

Every sentence earns its place: the purpose and scope come first, followed immediately by an example and the key constraint. There is no filler or 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?

Given a generic GET tool with no output schema and readOnly annotations, the description provides enough to invoke it correctly by pointing to the API documentation, giving a path example, and stating that only GET is allowed. It could be stronger by noting the expected response shape or how errors are returned, but the docs link covers most unknowns.

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% and already defines the path prefix and query format. The description adds a concrete example path (/v1/integrations), which gives the agent a useful pattern beyond the schema's abstract constraints, though it does not add meaning for the query parameter.

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 specific verb and resource ('perform a GET against any documented Spot AI API path') and identifies itself as an 'Escape hatch,' which distinguishes it from the specific endpoint tools among its siblings. The example path and constraint ('Only GET is supported') further pin down exactly what the tool does.

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 'Escape hatch' framing implies this is for endpoints not covered by dedicated tools, and the docs link tells the agent where to find valid paths. However, it never explicitly names when to prefer a sibling tool or when not to use this generic endpoint, so it falls short of full when/when-not guidance.

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