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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is fully covered externally. The description adds the HTTP route and operation ID for traceability but says nothing about what the 'accounting-impact indicators' actually mean, whether results are paginated, or what happens for an unknown lease id.

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?

Three short sentences, with the content description front-loaded before the route and operation metadata. The operation ID string is boilerplate but ties directly into the describe_operation pointer, so it earns modest keep.

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 read-only GET with no output schema, the definition says what domain of data comes back but not its shape, granularity, or the meaning of the three named indicator groups. Combined with zero parameter documentation, an agent can call it but cannot predict or interpret the response well.

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 carries the burden, yet it never explains the parameters. The route /api/leases/:id/rent-context implies the required id is a lease identifier, but the separate `query` object parameter is entirely undocumented in both schema and text.

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?

Names a specific verb (Read) and a concrete resource set (rent sources, option boundaries, accounting-impact indicators) and pins it with the route GET /api/leases/:id/rent-context. It distinguishes itself from the many other lease sub-resource siblings only implicitly through the route, not through an explicit 'unlike X' statement.

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?

There is no statement of when to reach for this versus near neighbours such as get_leases_by_id_rent_schedules_by_sche or get_accounting_leases_by_id_measurement_. The only forward pointer is to describe_operation for request schemas, which is format help rather than usage guidance.

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