list_practices_for_concern

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

With no annotations, the description carries the burden and does well by disclosing the data source (public NRCS CART spreadsheet, 'Assoc Ag Land' points), the listed fields (code, name, points), and the advisory, non-formal nature. It lacks mention of permissions or side effects, but these are unlikely for a read-only list operation.

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 concise, front-loaded with the primary purpose, and uses every sentence to add value: source, output fields, and advisory caveat. No unnecessary words or repetition.

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?

The description provides essential context for a simple lookup tool: purpose, data provenance, output fields, and the advisory nature. While it doesn't detail parameter handling or point interpretation, the presence of an output schema covers return values, making this sufficient for the tool's complexity.

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 single 'concern' parameter is not explicitly described; only the tool name and description imply it specifies the concern to query. With 0% schema coverage, the description adds no format, allowed values, or context for this parameter, leaving the agent to guess its exact semantics.

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 lists NRCS conservation practices associated with a concern, with specific verb 'list' and resource 'practices for concern'. It also distinguishes itself from sibling tools like list_concerns and get_concern_details by focusing on practices rather than concerns themselves.

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 implies usage for advisory discussions and notes it is not a formal practice plan, but it does not explicitly state when to choose this over alternatives. It offers context but no direct exclusions or comparisons to sibling tools.

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