planet_search

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

Discloses key behavioral traits (resolution, coverage, API key requirement) but omits details like pagination, rate limits, or error handling. Without annotations, the description carries full burden, and while adequate, could be more comprehensive.

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?

Extremely concise with two sentences, front-loading the purpose and essential requirement. Every word earns its place without 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?

Sufficient for basic understanding but incomplete without output schema or mention of return values. Given the tool's complexity and 7 parameters, more detail on results structure would improve completeness.

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%, so the description adds limited value beyond parameter names and types. It provides catalog context but no additional meaning for individual parameters, earning a baseline score.

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?

Clearly states it searches Planet Labs satellite imagery catalog with specific resolution and coverage details, differentiating it from siblings like landsat_search or sentinel_search.

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?

Mentions the required API key, providing a necessary usage condition, but lacks explicit guidance on when to use this tool vs alternatives or when not to use it.

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