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

With no annotations, the description carries the full behavioral burden. It does disclose what is returned ('full text and tables'), which implies a read-only fetch, but says nothing about return size, pagination, or permissions for potentially large Schedules, and there is no output schema to cover that gap.

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 core purpose is front-loaded in the first sentence, and the examples are compact and readable. The '7' example largely restates the 'Seventh' example, which is a minor redundancy rather than waste.

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 single-parameter read tool with no output schema, the description covers what the tool returns and the full range of schedules. It omits any note on response size or how the returned Schedules relate to the appendices and schedule-listing siblings, which leaves an agent slightly under-informed.

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 parameter is already documented. The examples reinforce that '7' and 'Seventh' are equivalent ('Same as Seventh'), which is a small confirmation of the schema's claim rather than new syntax or constraint detail, so the baseline 3 holds.

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 verb and resource ('Get the full text and tables of a specific Schedule of the Constitution of India') and bounds the scope ('all 12 Schedules'). This clearly separates it from the list-style sibling (list_constitution_schedules) and from get_constitution_appendix, though it never names those siblings explicitly.

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 examples imply how the tool is called but never state when to use this tool versus list_constitution_schedules or get_constitution_appendix. There are no exclusions, prerequisites, or alternative-routing guidance, leaving usage to inference.

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