property_by_roll

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

With no annotations, the description is the only source of behavioral context; it discloses that the result is a single record and makes a performance claim ('faster than search'). It doesn't address error/not-found behavior or authentication, though the output schema covers the success shape.

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?

Two compact sentences, no filler, and the main purpose is front-loaded. Efficient.

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?

For a simple lookup with an output schema, the essentials are present, but the role of the required city parameter is unexplained and could mislead an agent into thinking roll numbers are globally unique. The sibling landscape reinforces search-vs-lookup, which helps, but the city gap keeps it from being fully complete.

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 0%, so the description needed to clarify both city and roll_number. It only says roll number, implying the lookup is purely by roll number while city is also required, leaving the agent with an incomplete mental model.

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?

States a specific action ('Get') on a specific resource ('a single property assessment record') keyed by roll number. Distinguishes itself from property_search by noting it's faster when the roll number is already known.

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?

Explicitly tells the agent to use this when the roll number is already known and pitches it as faster than search. It doesn't list exclusions or compare against property_report/property_top, but the main alternative is clear.

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