shodan-account-profile

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

With no annotations, the description carries the full burden. It discloses the authentication requirement and lists the returned fields, but does not mention potential failure modes, rate limits, or other behavioral aspects. It is adequate for a simple read-only profile endpoint but not rich.

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 short and front-loaded with the primary purpose. It includes a brief list of return fields and a note about the API key. The final 'Returns' line is slightly redundant with the previous sentence, but overall it is concise and well-structured.

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 the tool's low complexity, an output schema that likely covers return values, and full parameter documentation in the schema, the description provides sufficient context: purpose, key fields, and authentication requirement. It is complete enough for an agent to use it correctly.

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 description coverage is 100% — the only parameter 'timeout' is fully described in the schema. The description does not add any extra meaning to the parameter, so baseline 3 is appropriate.

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 clearly states the tool's purpose with a specific verb ('Get') and resource ('your Shodan account profile information'). It is distinct from most siblings, but does not explicitly differentiate from the similar 'shodan-api-info' tool, which might also relate to account or API details.

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 description provides a prerequisite (API key) but does not explain when to use this tool versus alternatives. There is no explicit when-to-use or when-not-to-use guidance, and the presence of 'shodan-api-info' as a sibling creates potential ambiguity that is not addressed.

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