get_geomi_applications

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

No annotations are provided, so the description carries the full burden. It discloses that API Keys are secret and should be kept secure, which is useful behavioral context. However, it doesn't mention authentication requirements, rate limits, pagination, or what happens if no organizations exist. The security warning adds value but leaves other behavioral aspects unspecified.

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 three sentences with some redundancy (e.g., mentioning Geomi twice in the first sentence). The first sentence clearly states the purpose, but the second sentence about Geomi being an 'essential toolkit' is promotional rather than functional. The last two sentences about filtering are useful but could be more concise.

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 no annotations, no output schema, and 0 parameters, the description provides adequate context about what data is retrieved and how to interpret it. However, it lacks details on return format (e.g., structure of organizations/projects/applications), error conditions, or authentication needs, leaving gaps for a tool that handles sensitive API keys.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, maintaining focus on the tool's purpose and usage. This meets the baseline for tools with no parameters.

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 retrieves Geomi Organizations along with their projects, applications, and API Keys. It specifies the resource ('Geomi Organizations') and the associated data, but doesn't explicitly differentiate from sibling tools like 'get_specific_aptos_resource' or 'list_aptos_resources' that might also retrieve Geomi-related data.

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 implied usage guidance by explaining how to filter results for specific API key types (full node vs. gas station), but doesn't explicitly state when to use this tool versus alternatives like 'get_specific_aptos_resource' or other Geomi-related tools. No explicit exclusions or prerequisites are mentioned.

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