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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds value by stating that data is RERA-verified and listing the returned fields: builder, locality, status, possession date, registration date. This is useful behavioral disclosure beyond the annotations.

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 three short, purposeful sentences: purpose, usage context, and return fields. Every sentence earns its place with no filler or redundant elaboration.

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 read-only tool with one parameter, the description is largely complete: it explains when to use it, what it returns, and the data source is noted as RERA-verified. A small gap is the lack of mention of not-found or invalid RERA number behavior, but this is minor given the simplicity and the output field list.

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%, so the description should compensate. It only restates the parameter concept as 'RERA registration number,' which is already clear from the property name rera_number and title 'Rera Number.' It adds no format, pattern, validation, or additional semantic guidance for the lone parameter.

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 states a specific verb and resource: getting full RERA-verified details of a Bangalore project by RERA registration number. It clearly distinguishes itself from search-oriented siblings like search_projects and get_project_insights by focusing on complete project details for a single known project.

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 explicitly says to use this after search_projects to get complete information on a specific project. This gives clear context for when to invoke it, though it doesn't explicitly mention when not to use alternatives like get_project_insights or get_builder_projects.

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