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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered externally. The description adds one genuinely useful behavioral fact — that the result is a join across three record sources, warning the agent the payload is composite rather than a raw dataset. It says nothing about result volume, missing-data behavior, or cost of the join.

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?

A single front-loaded sentence with zero filler; the resource and its composition are stated immediately with no redundant restatement of the title.

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?

No output schema and no annotation detail means the description must explain the returned structure, yet it does not say what fields a 'profile' contains, whether records are nested per source, or how district-only calls behave. For a three-source join with three undocumented parameters, this leaves the agent materially under-informed before calling.

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 full burden and provides nothing: it never explains that district is required, that omitting neighborhood yields district-wide results, or what limit governs (neighborhoods returned? records per source?). An agent must guess from bare field names.

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 ('return a joined neighborhood profile') and names the three source record types (social, building, earthquake scenario), which tells the agent this is a composite/aggregate endpoint. It does not explicitly contrast with siblings like istanbul_nearby or istanbul_datastore_query, but the resource is distinctive enough that confusion is unlikely.

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?

Usage is only implied: the profile is scoped per neighborhood, so an agent can infer it should be used when a location-level summary is wanted. There is no statement of when to prefer this over istanbul_nearby, istanbul_datastore_query, or the individual source endpoints, and no prerequisites or exclusions are given.

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