teslamate_query_suggestion

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It mentions returning schema discovery but does not explain what that entails (e.g., JSON schemas, markdown?). No mention of side effects, permissions, or performance. For a tool that presumably queries internal definitions, more transparency is needed.

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 description is a single sentence of moderate length, front-loaded with the main action ('Recommend'). Every word contributes to purpose. It is appropriately concise for the tool's simplicity, though adding a brief parameter explanation would not harm conciseness.

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 3 parameters, no output schema, and no annotations, the description is incomplete. It fails to explain the input parameters' semantics, return format, or how recommendations are generated. An agent would lack critical information to use this tool effectively.

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% (no parameter descriptions in schema). The description adds limited meaning: it hints that 'query' is a user query, and 'optionally return schema' maps to includeSchemas. However, it does not explain maxRecommendations. For low coverage, the description should compensate more thoroughly.

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 'Recommend the best TeslaMate MCP tools for a query and optionally return schema discovery', which clearly identifies the tool's purpose as a recommendation engine. It distinguishes enough from siblings like teslamate_list_endpoints (which lists endpoints) and teslamate_api_request (which makes raw requests). However, 'schema discovery' is ambiguous—it could be improved by specifying what schema means (e.g., tool definitions).

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?

No explicit guidance on when to use this tool versus siblings. The description implies it's for tool selection, but does not specify scenarios where alternatives (e.g., direct API request) are more appropriate. No 'when not to use' or prerequisite conditions.

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