monitor_crop_phenology

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does add context by noting 'Automatically samples cloud-free Sentinel-2 observations' and 'Zero-config,' which tells the agent the tool handles data selection. However, it does not mention any limitations, processing time, data availability constraints, or whether the operation is purely read-only in terms of external side effects.

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 well-structured with clear sections: purpose, args, returns, references. The essential information is front-loaded. The scientific references at the end add credibility but do not help an agent select or invoke the tool, so they keep it from a perfect conciseness 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 an output schema and only one required parameter, the description is largely complete: it covers all parameters, the return summary, and the automatic Sentinel-2 sampling behavior. However, it omits details like valid year ranges, bbox size limits, or error conditions, which would be useful for an agent handling edge cases.

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 0%, but the description's Args section fully compensates. It explains bbox format (WGS84 coordinates), year default, crop_type examples, and format enum values ('summary', 'geojson', 'csv'). This gives the agent everything needed to set each parameter correctly, far beyond the bare schema.

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 opens with a specific verb and resource: 'Monitor agricultural crop phenology, growth trajectories, and vegetative anomalies across seasonal cycles.' It further specifies exact outputs (SOS, POS, EOS, drought stress vs baseline), making it clearly distinct from sibling tools like calculate_spectral_index or analyze_reservoir_drought. An agent can confidently recognize this as the tool for crop growing-cycle analysis.

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 conveys clear context: use this tool when you need to monitor crop phenology, seasonal growth, or vegetative anomalies. The 'Zero-config' note suggests it is a turnkey option, but it does not explicitly mention when not to use it or name alternative tools, so it stops short of full guidance.

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