planet_metadata

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

With no annotations, the description must disclose behavioral traits. It states it fetches metadata and requires an API key, but does not clarify if it is read-only, the nature of the metadata, rate limits, or response structure. This is insufficient for safe agent invocation.

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 concise sentence, but it is under-specified for a tool with two parameters and no output schema. While efficient, it sacrifices necessary detail, earning a middling score.

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 has no output schema, no annotations, and two parameters, the description should explain what metadata is returned and how to use it. It fails to provide this, leaving significant gaps for an agent to understand the tool's behavior.

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%, so baseline is 3. The description adds no extra meaning beyond the schema's parameter descriptions ('Planet item ID', 'Item type'). It does not provide examples or clarify usage context, so it meets but does not exceed the baseline.

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 it retrieves detailed metadata for a Planet Labs item, which is a specific verb-resource pair. This distinguishes it from sibling tools like planet_search (searching for items) and planet_stats (statistics), though it doesn't elaborate on what 'metadata' entails.

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 mentions the requirement of PLANET_API_KEY but provides no guidance on when to use this tool versus alternatives like planet_search or planet_thumbnail. It lacks context on prerequisites (e.g., obtaining an item_id) or usage scenarios.

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